| re: Deploying Access 2003 runtime
Many people use third-party installers such as Wise or InstallShield to
package their Access databases for distribution. However, they must still
obtain the Visual Studio Tools for Office 2003 System or appropriate
Developer Edition, to have a license to distribute the runtime support.
I am not aware of anyone using the Visual Studio installer for Access
database applications, and don't know if you can or cannot. After all,
Microsoft Office (including Access) is "Not Yet Dot Net". I am sure it does
not include a Wizard for Access database applications, but would not be
surprised if it could be used with sufficient time and effort, assuming that
it can package un-managed code applications done in C++.
Larry Linson
Microsoft Access MVP
"Mister_d" <mister_d77@hotmail.com> wrote in message
news:1114q8inq8kn406@corp.supernews.com...[color=blue]
> When deploying a solution using the Access 2003 runtime engine, do you[/color]
have[color=blue]
> 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[/color]
not[color=blue]
> match the master copy, the master is downloaded to the client computer,[/color]
then[color=blue]
> the database is launched. That way when the front end is updated all I[/color]
have[color=blue]
> 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.
>
>[/color]
| 
