I assume a repair has been done?

Post #147,077 by ChrisR 3/19/04 1:07:41 PM Reply	I assume a repair has been done? Have heard of older versions of Access (97 i think) that would get the database in a funk, and you'd have to recreate the database over again. If you assume that it's a programmer problem, then you'd have to look and see what program was locking the records and not committing or rolling back the transactions. In the worst case, a program that causes access to lock up, may be the source of the locks.
Post #147,081 by acagle 3/19/04 1:32:06 PM Reply	Dunno. But I have an update. The .ldb file is not being deleted when she closes. ANd she got this message from a tech support person: "I have looked into your in accordance with the log database files it is telling me that you are not closing your record set and connection object. Please review this code this is where the problem lies." Something is not closing the ODBC connection apparently. That doesn't explain the lack of ability to add records though.
Post #147,091 by ChrisR 3/19/04 3:31:15 PM Reply	Depends on the kind of a lock Some transactions require the whole table to be locked for update. That is, you don't want to have the set change on you in the middle of the read - unless you want dirty reads.
Post #147,115 by FuManChu 3/19/04 5:02:59 PM Reply	That 'something' is the developer. Explicitly close connections instead of letting them just fall out of scope. Goes double when errors are raised.

Welcome to IWETHEY!