usmc-ratman
Registered User.
- Local time
- Today, 00:51
- Joined
- May 27, 2005
- Messages
- 20
[grab a drink and get comfortable, may be a bumpy ride 
]
All systems using WinXp SP3, database built & maintained with Access 2k, some access 2003 systems are using it as well.
The database is split (FE/BE), the BE residing on a 1TB server, with a total of 13 users on an office network, each computer has the FE and use linking of L: drive for the server. The mapping of L: is created using the 'net use' command at boot up, this way if the mapping is lost at anytime, will be re-established when the user reboots the machine.
K - Now for the problem....
Originally when the database was built, there were 3 ppl using it. Over the past 4 years, that number has grown, as has the number of records, etc. More frequently now, users will be entering data, on different client records, but into the same table (a billing subform to the main client's information). When a user enters a new billing line, it will give the error that the record cannot be create because it would cause a duplicate record to be created (something similar to that).
I know that this is happening because records are being added to the "billing" table at approximately the same time, and both are attempting to create a new record with the PK being the same. FYI: The billing subform is one of 6 subforms on the main client form, in a tabbed control.
A temporary work around for this is, I have told them that if they get that error, click the refresh button on the main form (a simple button assigned to the F9 key function), and then re-enter the line in the billing subform. No real biggie, but it was not giving this error before. I dont know if it is just because so many ppl are entering data now, as opposed to before, or if there may be some type of corruption or problem with MS Jet engine or something like that.
Any suggestions or brain-storming on this would be appreciated. Or suggestions on a script that would trigger off that error code, copy the information in the unsaved billing line, refresh the form, and paste/append the data back (like the error was never given).
Thank you,
John R.
]All systems using WinXp SP3, database built & maintained with Access 2k, some access 2003 systems are using it as well.
The database is split (FE/BE), the BE residing on a 1TB server, with a total of 13 users on an office network, each computer has the FE and use linking of L: drive for the server. The mapping of L: is created using the 'net use' command at boot up, this way if the mapping is lost at anytime, will be re-established when the user reboots the machine.
K - Now for the problem....
Originally when the database was built, there were 3 ppl using it. Over the past 4 years, that number has grown, as has the number of records, etc. More frequently now, users will be entering data, on different client records, but into the same table (a billing subform to the main client's information). When a user enters a new billing line, it will give the error that the record cannot be create because it would cause a duplicate record to be created (something similar to that).
I know that this is happening because records are being added to the "billing" table at approximately the same time, and both are attempting to create a new record with the PK being the same. FYI: The billing subform is one of 6 subforms on the main client form, in a tabbed control.
A temporary work around for this is, I have told them that if they get that error, click the refresh button on the main form (a simple button assigned to the F9 key function), and then re-enter the line in the billing subform. No real biggie, but it was not giving this error before. I dont know if it is just because so many ppl are entering data now, as opposed to before, or if there may be some type of corruption or problem with MS Jet engine or something like that.
Any suggestions or brain-storming on this would be appreciated. Or suggestions on a script that would trigger off that error code, copy the information in the unsaved billing line, refresh the form, and paste/append the data back (like the error was never given).
Thank you,
John R.
