-
I am creating an application that will use a couple of local Access Database tables. These tables will be in principle for use solely by this application.
I know how to create the database initially, but how do I set it up when I distribute the application ? Can this be done by an install utility (I also may need to create a dsn) Or do I need to do it programatically when I run the application, and make it detect whether the tables exist or not... (if yes, any guides on how to do this ?)
Everything may not be explained in this NG, but any pointers to good books on the subject will be appreciated...
Thanks !
-
You can add the database into the install set when you create it. I use installshield to create install sets and it give you a lot of options as to what to do with the files. I don't think the VB package and deployment wizard is as flexible but you can add further files if needed.
Regards
chris
-
You can do a couple of things. What I like to do is create the database in the program. That way if something happens to their current database you can just delete it and then the program will create it automatically if the database does not exists.
You could also create the database, like you did, and then in the setup wizard just add the database. The screen you do that on I believe is 'File Summary' screen. Just hit the add button and find your database. This is for VB 5.
