Here is my problem. I have an packaged VB application which includes a separate Microsoft Access database (initial database was created using Office 97 version of Access). An user should ideally be able to modify the Access database if they want to use their own specific information with the VB application. However, if the VB application/Access Database is installed on machine with newer versions of Access, the user runs the risk of destroying database if they choose to make modifications to it. Any ideas on how to handle this? The installation who be independent of Windows OS and Microsoft Access versions.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
I have VB app that uses Access file - install with Win OS
- Thread starter LcdCyn
- Start date
Similar threads
- Locked
- Question
