Hi again, Mike,

>What is the error? What message is being returned to you?

OK, we've done some further testing as follows:

We recreated our database with empty tables. We then used our application to create a single record in one of the tables. We edited this record by adding data to a memo field and issued a tableupdate().

There was a long delay followed by the tableupdate() returning .f.

On inspecting SQL Server, we noticed that the transaction log was completely full [it was set to 2Mb].

So, we resized the transaction log to 10Mb and repeated the test. Again, we had a long delay [longer this time] followed by the tableupdate returning a .f.

We again had a look at SQL Server and noted that the transaction log was again full.

Any idea what's generating all this stuff in the transaction log ?
The amount of data we are adding to the memo box is less that 200 Kb, say.

I'm guessing that the problem with the transaction log is what is causing the update to fail. When these tests were carried out, only one user was accessing the system and all edits were made to a single record in one of the tables in the database, all other tables remaining empty.

Best.

Matt.