- Joined
- Jun 17, 2005
- Messages
- 3
- Reaction score
- 0
Hey all,
If anyone can help, got a major issue.
I'm re-egineering a reporting system for a company I am employed with, but the current system, which needs to continue running while I implement the new system, has developed a strange problem.
The current system operates through Microsoft Access, but uses SQL Server database tables as its source, not Access' proprietry database format.
We have a collection of forms, some of which have subforms on which reference other tables. Now, the problem which has developed is, when data is changed on the main form, and the user tries to perform actions on the sub forms, they are greeted with a lovely 'write-lock' message, and they are forced to drop the changes they made to the original data.
I have no idea why this has suddenly happened, and am wondering if you guys have a solution?
If anyone can help, got a major issue.
I'm re-egineering a reporting system for a company I am employed with, but the current system, which needs to continue running while I implement the new system, has developed a strange problem.
The current system operates through Microsoft Access, but uses SQL Server database tables as its source, not Access' proprietry database format.
We have a collection of forms, some of which have subforms on which reference other tables. Now, the problem which has developed is, when data is changed on the main form, and the user tries to perform actions on the sub forms, they are greeted with a lovely 'write-lock' message, and they are forced to drop the changes they made to the original data.
I have no idea why this has suddenly happened, and am wondering if you guys have a solution?