theriver

Ah yes, the old "It works fine for us" defence ;-) The problem is that developers will often stress test applications under 'perfect' conditions, e.g. on a test server that’s doing nothing else and on a quiet network. Of course these things then get run from a busy server over a congested network….. I don’t know anything about this application, for example if users are just reading from it or if it gets written to as well, but: - Is there any kind of inbuilt maintenance routine? Does running that help? - If not does opening the data file in Access and running a compact / repair help? (backup first!) Try making access to the data file as quick as possible. For example, are the PC’s on-access virus scanning the data file? Try excluding it. If the users aren’t writing to the database, i.e. it’s just acting like a read-only data repository, does the data file have to live on the network? Can it be installed locally?

Sure - I've put together an example that demonstrates the principle, just step through it. There are other ways to achieve the same thing, but this is probably the simplest. staging table demo.txt

Yes. Rather than import the XLS file into your SQL table, import it as a different table. You can then run a query to insert only the XLS records that don't exist in the SQL table. Although you presumably also want to update any existing rows as well, where they might be different. This also has an advantage that you don't have to delete the SQL data table before you start, so if there's a problem with the import it doesn't leave you with a broken system.

I'd drop it all into E:, that way you keep as much as possible off of c: (which at 40Gb will appear quite full anyway) and the installer takes care of setting up everything in a useful location with the right permissions etc.

Tagline: They're back - and this time, they've installed Avast!

Looking for the registrar with whois should do it: Whois Lookup, Domain Availability & IP Search - DomainTools

I don't know much about SIMS these days, but this is a SQL error - meaning that the application has successfully logged in to the SQL Server. The account SIMS is logged in with is trying to execute one of the stored procedures, but does not have enough privilege.

Even where there is no legal weight it's certainly enough to raise eyebrows, and will likely cause a stir, particularly for those initiating it. Just a reminder that this is a public forum, tread lightly . . . . .

Did it live up to expectation? I saw a few minutes here and there, and it reminded me that I've become middle aged, don't go out on a Friday any more and have too much going on to watch TV :-)

So, what if an adult walks into the school wearing one of these gadgets?

If this was me, I'd: - create a temp table with the name, grade, subject, season as text fields - have a procedure that goes through the SIMS export line by line: For each row: insert into mytemptable (name, grade, subject, season) select name, english autumn, 'english', 'autumn' insert into mytemptable (name, grade, subject, season) select name, english spring, 'english', 'spring' insert into mytemptable (name, grade, subject, season) select name, maths summer, 'maths', 'summer' insert into mytemptable (name, grade, subject, season) select name, maths spring, 'maths', 'spring' which would give something that looks a bit like name grade subject season CAM A english autumn CAM A english spring CAM A maths summer CAM A maths spring Once it's in the temp table I'd do whatever other transformations are required and then insert the new rows into the real table.

They broke the theme music!

Does Disco 2000 count? (Well, half a mark?)

In your //Add Entry to DataBase section you have a line that starts: string strQuery = "insert into Bathroom And that's going to try and add a row to the Bathroom table. I reckon you're lacking a Bathroom table. The next problem you will have will relate to this: "insert into Bathroom (Name, Description, ToolTip, FilePath) values(@Name, @description, @ToolTip, @CategoryId, @filePath)"; You've specified 4 columns in the table, but you're inserting 5 values.

I thought that an automatic lock to prevent thread necromancy was mooted a while ago?