PDA

Click to See Complete Forum and Search --> : [RESOLVED] Deploying with Inno problem


coolcurrent4u
Nov 12th, 2009, 02:34 AM
Hi all,
i have been battling this for three weeks now.
i have a database app that uses access 2003 and jet 4.0 oledb, i am having problem packaging the app with inno and including jet 4.0. i tried the help on inno website, but it is not helpful.

i have also included mdac 2.5 since 2.6 above no longer includes jet.

what i need to know is what files i need to package my app, so that a system without access can still use it without any problem.

if you have ever packaged an app with access 2000-2003,to install on system without office or Access, i really need your help here.

can you please help me out

akhileshbc
Nov 12th, 2009, 02:57 AM
First try using the PACKAGE AND DEPLOYMENT wizard to create a setup. Then you will see a folder called Support, which is a subfolder to where your setup is created or stored. This folder(support) contains all the files that are needed to icluded, like dlls, ocxs, etc...
Then use inno to pack those files too...
Hope you understand...:)

coolcurrent4u
Nov 12th, 2009, 06:01 AM
First try using the PACKAGE AND DEPLOYMENT wizard to create a setup. Then you will see a folder called Support, which is a subfolder to where your setup is created or stored. This folder(support) contains all the files that are needed to icluded, like dlls, ocxs, etc...
Then use inno to pack those files too...
Hope you understand...:)

i have done this but still does not work for me. P & DW does not includ the jet files, i use jet4.0.oledb with access2003

any further help

si_the_geek
Nov 12th, 2009, 06:26 AM
Please post in the correct forum - thread moved to the 'Application Deployment' forum

As your program uses Jet 4, you should clearly be installing Jet 4. You can get it via the MDAC link in my signature.


If the computers you are installing on are Windows 2000 or earlier, you should also install MDAC (preferably 2.7 or higher).

coolcurrent4u
Nov 13th, 2009, 07:14 AM
Please post in the correct forum - thread moved to the 'Application Deployment' forum

As your program uses Jet 4, you should clearly be installing Jet 4. You can get it via the MDAC link in my signature.


If the computers you are installing on are Windows 2000 or earlier, you should also install MDAC (preferably 2.7 or higher).

pls you'll have to help me on this one, i have tried serveral attempst without success?

here is my ddetails, my app uses access database (2003)

what does this error means

The connection cannot be used to perform this operation. It is either closed or invalid in this context.

could it be because it can see the database?

si_the_geek
Nov 13th, 2009, 08:00 AM
That error is nothing to do with installation - it is because of a mistake in your code.

It is happening because you are trying to use a connection (maybe as a parameter to rs.Open) when the connection is not open - either because it hasn't been opened yet, or because it was open but has been closed.

coolcurrent4u
Nov 14th, 2009, 03:53 AM
That error is nothing to do with installation - it is because of a mistake in your code.

It is happening because you are trying to use a connection (maybe as a parameter to rs.Open) when the connection is not open - either because it hasn't been opened yet, or because it was open but has been closed.

TRhansk for the reply si_the_geek, but i do open the connection, i think i figured part of the problem.

i have a dll that does all dbconnections the dill is installed in app/lib, abd the database exist in app/data.

in my code i use app.path & "/../data/db.mdb to reference the db. it works fine in vb, but not in compiled,installed app

si_the_geek
Nov 14th, 2009, 04:31 AM
You shouldn't be using different paths in VB, you should be using the same ones as you do when it is compiled.

Move the files that VB uses to the correct place, and change your code to suit it.

coolcurrent4u
Nov 16th, 2009, 11:17 AM
ok Si i took the easy way out. i installed all the files in tha same directory. this resolved the problem. thanks