Hi All,
I'm using MS Access 2003 SP3.
I've created front / backend databases which are used over a LAN / WAN and VPN. Both databases are about 5MB each.
The backend keeps getting corrupted and most times when opening the backend directly through MS Access it has repaired itself.
I've about 20 users who are based local to the server, another 10 in another office(slow isdn type link) and 30 occasional users who connect over the internet using a vpn connection.
My guess is that the database is corrupting itself when the vpn connection falters or times out.
I've implemented code that does an application.quit so I can get everyone out of the backend database so I can repair it, but it doesn't always work as I imagine the front that had a problem will be unable to respond to the timer event to quit.
So, my questions...
Is there a timeout setting I can change so that the frontend waits a bit longer for the backend to respond?
If there is a problem with the frontend updating a record( I tend to use recordsets), can I capture this and maybe retry or atleast log what table was being updated?
Is there any option to increase the logging that Access write to the Event log?
I have 9 tables in the backend, one of which has hit the column limit a couple of times, but only has 500 rows. I know this sounds like bad design and probably could be better, but there is very little redundancy in each row. Would it be beneficial to split this table up as a way to reduce corruption (I'm not too worried about performance at the mo.)?
Should I try to use transactions as a way to reduce corruption?
I'm about to turn off autocorrect and subdatasheets as this may help.
My boss is getting quite twitchy when a whole department is sitting waiting for me to get the database file unlocked so I can then repair it (hopefully) and then get everyone back online.
Thanks for reading this.
Kristian
I'm using MS Access 2003 SP3.
I've created front / backend databases which are used over a LAN / WAN and VPN. Both databases are about 5MB each.
The backend keeps getting corrupted and most times when opening the backend directly through MS Access it has repaired itself.
I've about 20 users who are based local to the server, another 10 in another office(slow isdn type link) and 30 occasional users who connect over the internet using a vpn connection.
My guess is that the database is corrupting itself when the vpn connection falters or times out.
I've implemented code that does an application.quit so I can get everyone out of the backend database so I can repair it, but it doesn't always work as I imagine the front that had a problem will be unable to respond to the timer event to quit.
So, my questions...
Is there a timeout setting I can change so that the frontend waits a bit longer for the backend to respond?
If there is a problem with the frontend updating a record( I tend to use recordsets), can I capture this and maybe retry or atleast log what table was being updated?
Is there any option to increase the logging that Access write to the Event log?
I have 9 tables in the backend, one of which has hit the column limit a couple of times, but only has 500 rows. I know this sounds like bad design and probably could be better, but there is very little redundancy in each row. Would it be beneficial to split this table up as a way to reduce corruption (I'm not too worried about performance at the mo.)?
Should I try to use transactions as a way to reduce corruption?
I'm about to turn off autocorrect and subdatasheets as this may help.
My boss is getting quite twitchy when a whole department is sitting waiting for me to get the database file unlocked so I can then repair it (hopefully) and then get everyone back online.
Thanks for reading this.
Kristian