Group:  Microsoft Access ยป microsoft.public.access.developers.toolkitode
Thread: packaging vb application with access db

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

packaging vb application with access db
humble.chetan[ at ]gmail.com 02.03.2006 18:47:02
after creating the vb package and including the access db file, i
wanted to check that if i remove the access db file from its source,
would it affect execution of the packaged application. i can clearly
see the access file in the package folder but, the application gives an
error if i change the path of the source access file( i.e. not the 1 in
the package folder), plz help?

Re: packaging vb application with access db
scott <scott[ at ]NoSpam_Infotrakker.com> 23.03.2006 14:49:29
On 2 Mar 2006 10:47:02 -0800, humble.chetan[ at ]gmail.com wrote:

[Quoted Text]
>after creating the vb package and including the access db file, i
>wanted to check that if i remove the access db file from its source,
>would it affect execution of the packaged application. i can clearly
>see the access file in the package folder but, the application gives
an
>error if i change the path of the source access file( i.e. not the 1
in
>the package folder), plz help?

Not sure what you mean - if your application requires the Access
database to function, then you must deploy it.

If you mean that AFTER you package the application, can you move the
database (like on your development machine), then you should be able
to do so. Depending on how you packaged it, all necessary files should
be included in the installer executable.

However, if you attempt to re-build your package AFTER moving a source
file, you'll have to tell the installer where the new location is.
Generally speaking, you should make sure to the maintain the folder
structure and filenames after deploying your application - makes
updates easier (espeically with the Windows Installer). I normally
xcopy them to a network drive for safekeeping, then re-import them as
needed. I also keep a separate directory just for deployed items -
those items are never touched once a package is released to endusers.

Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net