I have been contracted to redevelop 10 VB 3.0 applications and one Access 2.0 database for a bank. The applications will be redeveloped in VB 6.0 and the Access database will be converted to Access 7.0. The bank's configuration is: 3 branches where one may be considered headquarters; at the headquarters, there is one NT Server where the database and applications reside; there are two T1 lines connecting each of the other branches; each workstation connecting to the server runs Windows 95; there are approximately 6-10 users who may simultaneously access the database at one time.
Issue: the VB 3.0 apps were coded by an amateur (not that I am an expert) who might have 40 text boxes on one form with names Text1, Text2,...Text40, who would place an END statement prior to code that he have liked executed, etc.. Occasionally, the bank experiences database corruption. When I recode the apps in VB 6.0, I need to be aware of certain practices, such as, Record Locking, Closing Recordsets, etc..
Without referencing a book, might someone suggest a model that includes practices to avoid corrupting the database and to ensure data integrity. I assume I should use the Jet Engine to connect to the database.
Sorry for the lengthy question.