When deploying a solution using the Access 2003 runtime engine, do you have
to use the packaging wizard that comes with the Access 2003 Developer
Extentions, or can you use other packaging software such as the Visual
Studio packager?
The reason I ask it that I have created a small VB application that when
launched, compares the revision of the local database (front end) to the
revision of a master copy stored on a file server. If the revision does not
match the master copy, the master is downloaded to the client computer, then
the database is launched. That way when the front end is updated all I have
to do is post it to one location instead of going to each computer and
manually copying the new front end.
In this case, I need the packaging wizard to reference the executable
instead of the .mdb / mde file.
Thanks for any help you can provide,
Mike.