path not found

[matrik02]

I have Microsoft access 2003 . After deployment.. I test on my machine.. It work.. After I install on target machine and run the application.. It doesn't work. I got this "Part not found" run time error '76' . I have put the DBMS.mdb at the right location.. Why it happend like this?

[lintz]

Is the MDB meant to be in the same folder as the EXE? If so you can you use App.Path in your app instead of hard coding (presume you have done this) the location of the database.

[matrik02]

During Deployment and package wizard. I include this MDB file in this package. I run it on other machine. I got this error message . Path not found. I put the file a same location in EXE file. On my machine It work fine.. I use

cs = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.path & "\DBMS.mdb" & ";Jet OLEDBatabase Password=macres;"

This is the Setup.LST

[Setup1 Files]
[email protected],$(CommonFiles)\ESRI,$(DLLSelfRegister),$(Shared),3/23/01 3:25:06 AM,40960,2.1.1.0
[email protected],$(CommonFiles)\ESRI\Raster\devices\ntx86,,$(Shared),1/12/06 11:36:50 AM,3394,0.0.0.0
[email protected],$(CommonFiles)\ESRI,$(DLLSelfRegister),$(Shared),3/23/01 3:25:06 AM,57344,2.1.1.0
[email protected],$(CommonFiles)\ESRI\MO_image\Devices\RasterFormats,,$(Shared),11/27/00 1:44:46 PM,3773,0.0.0.0
[email protected],$(CommonFiles)\ESRI\MO_image\Devices\NTx86,,$(Shared),11/27/00 1:44:46 PM,1733,0.0.0.0
[email protected],$(CommonFiles)\ESRI,$(DLLSelfRegister),$(Shared),3/23/01 3:24:44 AM,57344,2.1.1.0
[email protected],$(AppPath),,$(Shared),8/9/07 12:49:02 AM,299008,0.0.0.0
[email protected],$(CommonFiles)\ESRI,$(DLLSelfRegister),$(Shared),3/23/01 3:24:58 AM,765952,2.1.1.0
[email protected],$(CommonFiles)\ESRI,$(DLLSelfRegister),$(Shared),3/2/01 12:07:42 AM,86016,2.1.0.2
[email protected],$(CommonFiles)\ESRI\MO_image\Usr\Lib\NTx86\RasterFormats,,$(Shared),11/27/00 1:44:46 PM,23552,0.0.0.0
[email protected],$(CommonFiles)\ESRI\MO_image\Usr\Lib\NTx86\RasterFormats,,$(Shared),11/27/00 1:44:46 PM,99328,0.0.0.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:28 AM,319488,8.0.1.0
File13=@MDAC_TYP.EXE,$(AppPath),,$(Shared),6/26/98 12:00:00 AM,8124720,4.71.1015.0
[email protected],$(WinSysPath),,$(Shared),4/3/00 5:52:54 PM,151552,6.0.88.4
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/11/00 1:06:20 PM,397312,6.0.88.62
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,10/27/00 11:54:20 AM,176128,3.51.623.0
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,10/27/00 11:54:20 AM,294912,3.51.623.0
[email protected],$(CommonFiles)\ESRI,$(DLLSelfRegister),$(Shared),3/1/01 9:32:12 PM,139264,2.1.0.1
[email protected],$(AppPath),$(DLLSelfRegister),$(Shared),1/9/98 2:40:32 PM,66560,1.1.0.1
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 4:58:00 PM,647872,6.0.88.4
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 4:58:12 PM,244416,6.0.84.18
[email protected],$(CommonFiles)\ESRI,$(DLLSelfRegister),$(Shared),3/23/01 3:24:52 AM,94208,2.1.1.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/22/01 1:09:18 AM,319488,8.1.0.641
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/22/01 1:09:16 AM,1208320,8.1.0.641
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:26 AM,360448,8.1.0.631
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:26 AM,640862,2.0.1.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:26 AM,1065870,2.0.1.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:26 AM,611030,2.0.1.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/22/01 7:42:26 PM,352256,0.0.0.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/22/01 7:41:26 PM,131072,0.0.0.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:26 AM,8704,0.0.0.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:26 AM,9728,0.0.0.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:24 AM,3432448,8.3.1.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:24 AM,6144,0.0.0.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),3/14/01 2:27:24 AM,420864,6.0.612.101
[email protected],$(CommonFiles)\ESRI,$(DLLSelfRegister),$(Shared),3/23/01 3:24:32 AM,339968,2.1.1.0
[email protected],$(CommonFiles)\ESRI,,$(Shared),6/1/01 1:10:00 PM,958464,2.1.1.3
[email protected],$(CommonFiles)\ESRI,$(DLLSelfRegister),$(Shared),3/23/01 3:26:18 AM,1130496,2.1.1.0
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 4:58:00 PM,140488,6.0.84.18
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),12/6/00 1:02:36 PM,209608,6.0.90.43
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),4/3/00 8:05:58 PM,118784,6.0.88.4
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),12/6/00 1:02:06 PM,262328,6.0.89.88
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/22/00 4:58:00 PM,118976,6.0.88.4
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),12/20/02 2:02:44 PM,1077336,6.1.95.45
[email protected],$(WinSysPathSysFile),,,8/4/04 9:56:44 AM,343040,7.0.2600.2180
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),10/13/05 10:14:12 AM,151552,5.6.0.8825
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),3/30/07 7:09:40 AM,2267368,9.0.45.0
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/18/98 12:00:00 AM,299008,6.0.81.69
[email protected],$(WinSysPath),,$(Shared),6/18/98 12:00:00 AM,89360,6.0.81.69
[email protected],$(WinSysPathSysFile),,,10/27/00 11:54:20 AM,415504,3.51.2404.0
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,4/24/98 12:00:00 AM,252176,3.51.623.0
[email protected],$(WinSysPathSysFile),,,8/4/04 9:56:44 AM,380957,6.0.72.9589
[email protected],$(WinSysPathSysFile),,,8/4/04 9:56:48 AM,30749,6.0.1.9431
[email protected],$(WinSysPathSysFile),,,4/24/98 12:00:00 AM,123664,3.51.623.0
[email protected],$(WinSysPathSysFile),,,4/24/98 12:00:00 AM,24848,3.51.623.0
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,10/27/00 11:54:20 AM,1046288,3.51.2723.0
[email protected],$(MSDAOPath),$(DLLSelfRegister),$(Shared),4/27/98 12:00:00 AM,570128,3.51.1608.0
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/18/98 12:00:00 AM,77824,6.0.81.69
[email protected],$(WinSysPath),,$(Shared),8/4/04 7:21:44 AM,81920,2.81.1117.0
[email protected],$(WinSysPath),,$(Shared),8/4/04 9:56:44 AM,144384,5.1.2600.2180
[email protected],$(AppPath),,$(Shared),8/8/07 11:19:58 PM,5128192,1.0.0.0

[randem]

You are saying that when you install the app the database does not get placed in the app's folder?

[matrik02]

After I include the MDB file in the P&W during creating the setup program and install the package on the target machine, the path not found when I run my application on target machine. The database place at the application program after the installation on target machine. I don't know. I use ADODB .I also

include this
File13=@MDAC_TYP.EXE,$(AppPath),,$(Shared),6/26/98 12:00:00 AM,8124720,4.71.1015.

[randem]

Is the mdb file in the app folder after installation?

[matrik02]

Yes, It is in the application folder.
When I run this program I got as the attach file below in my application folder

[randem]

That looks like the protected database to me...

[randem]

BTW: You are including files you should not deploy, especially if deploying MDAC. Which MDAC are you deploying anyway?

[matrik02]

File13=@MDAC_TYP.EXE,$(AppPath),,$(Shared),6/26/98 12:00:00 AM,8124720,4.71.1015.0

I use Microsoft ActiveX Data Object 2.5 library. If I not deploy MDB file together in my package, I got this the file attach..

When I put the database in the application folder.. I got this Path not found '76'

[randem]

That is not a valid path with a space after c:\Project

MDAC_TYP.exe is not a version of MDAC. That is just a file name which could represent any MDAC version.

Run your app through ********** to see the difference.

[matrik02]

BTW: You are including files you should not deploy, especially if deploying MDAC. Which MDAC are you deploying anyway?

Should I deploy that file MDAC if I use Microsoft ActiveX 2.5 data object?No Visual basic installed on target machine

[randem]

What I am getting at is how do you know what MDAC that is?

[RobDog888]

Using the P&D Wiz you should not have to explicitly add the MDAC to it. It reads the reference from the vbp file and includes the used version.

The mdb is not a protected database but looks like it is rather locked which only means that it is opened already by some process or user.

What is the OS you are installing to? If its Vista then you need to install the mdb into a user specific folder or a publically shared forlder for all user access. It will generate a file not found error if you are installing it to the Program Files directory under your app.

[randem]

How could it use the correct version. Especially if they did not download it and name it MDAC_TYP.exe. That's a generic name...

[RobDog888]

Like I posted it should read the referenced version of mdac and package that. It appears that it may have been manually addeed.

[randem]

It will only be able to package the last MDAC installed for that will be the only MDAC_Typ.exe file they will have in the folder. It won't do any good for JET and DCOM though...

[RobDog888]

Well the member is using the P&D Wiz and hasnt replied with the extra needed info so until then it makes no use to discuss much else.

[randem]

He is getting that message because c:\Project \DBMS.mdb contains a space and should be c:\Project\DBMS.mdb if that is where his database is stored. He is definitely hard coding the path.

[RobDog888]

The only thing I can tell is that you deleted your post that was inbetween post #3 and #5 but #5 is now #4. Yes the space will be invalid. Usually you just click the "Add" button to select the extra file to add to the P&D Wiz setup.