VB3 app with Access 2.0 backend

Hello,

I am supporting a VB3 application with an Access 2.0 backend...  We are constantly plagued with DB corruption issues.  There are plans to replace the s/w in 2yrs and thus we are forced to help the existing app limp along until that time.  We regularly repair/compact the DB in efforts to pre-emptively avoid corruption issues, however, they continue to happen...

We've come up with several ideas to help minimize these problems...
1. restrict users editing the DB to one at a time (hence eliminating the possibility of multiple users causing corruption)
2. upgrade the backend to access 2000 (assuming that access 2000 can better handle multiple users and also assuming the VB3 is compatible with access 2000)
3. a complete re-write (front-end/backend) which will be time consuming and costly.

Any comments   I'm particuarly interested in the feasibility of option #2.

Thanks.
  


Answer this question

VB3 app with Access 2.0 backend

  • VB3 app with Access 2.0 backend