VB/Access/INNO setup not working/Danial?/Frigginjerk?

Hello, forum-ers

I have a project developed in VB 6 which reads and writes to an Access database. In other words, the Visual Basic is the front end to the Access database. It works fine on my computer (which is Windows XP Home and has Office Professional 2002). What I want to do is create a setup to install it on other computers. I am using a test computer which has Windows 98 but no Office Professional. My setup is an INNO script.

The result of my setup on the other computer is that the program reads the data, but it will not write data. Maybe it is a security problem. The owner of the Access database is Admin. This is on the first computer. On the second computer there is no Access (intentionally), so no Access settings can be changed on that computer. Any settings would have to be made on the first computer before installing. I don't know how to set it so no one owns it or if this is possible.

Also, the 2nd computer won't allow me to delete the Access database. (Again, security?) I can delete all the other files.

So, I'm not sure if it's security or what. Can anybody confirm or deny that it's security or have any other suggestions to help me get my VB program to write data instead of just read it on the 2nd computer? I have never installed a VB-plus-Access program, so it could be something obvious.

Thanks.

Robert


This is my INNO script:




[Setup]
AppName=Distribution Management
AppVerName=Distribution Management
DefaultDirName={pf}\Distribution Management
DefaultGroupName=Distribution Management
UninstallDisplayIcon={app}\Distribution_Management.exe
Compression=lzma
SolidCompression=yes

[Files]
Source: Distribution_Management.exe; DestDir: {app}
Source: adenamsm.bmp; DestDir: {app}
Source: custs.frm; DestDir: {app}
Source: custs.frx; DestDir: {app}
Source: DataEnvironment1.DCA; DestDir: {app}
Source: DataEnvironment1.Dsr; DestDir: {app}
Source: DataEnvironment1.dsx; DestDir: {app}
Source: DataProject.vbw; DestDir: {app}
Source: DataReport1.DCA; DestDir: {app}
Source: Distribution_Management.PDM; DestDir: {app}
Source: Distribution_Management.TXT; DestDir: {app}
Source: Distribution_Management.vbp; DestDir: {app}
Source: Distribution_Management.vbw; DestDir: {app}
Source: dlgFindFunction.frm; DestDir: {app}
Source: DM1.frm; DestDir: {app}
Source: DM1.frx; DestDir: {app}
Source: Form3.frm; DestDir: {app}
Source: Form5.RtListBK.frm; DestDir: {app}
Source: Form5.RtListBK.frx; DestDir: {app}
Source: frmCustList.frm; DestDir: {app}
Source: frmCustList.frx; DestDir: {app}
Source: frmCustMenu.frm; DestDir: {app}
Source: frmCustomers.frm; DestDir: {app}
Source: frmCustomers.frx; DestDir: {app}
Source: frmDM1.frm; DestDir: {app}
Source: frmDM1.frx; DestDir: {app}
Source: frmMain.frm; DestDir: {app}
Source: frmReportsMenu.frm; DestDir: {app}
Source: frmReportsMenu.frx; DestDir: {app}
Source: frmRouteList.frm; DestDir: {app}
Source: frmRouteList.frx; DestDir: {app}
Source: frmRtList.frm; DestDir: {app}
Source: frmRtList.frx; DestDir: {app}
Source: frmSplash.frm; DestDir: {app}
Source: frmSplash.frx; DestDir: {app}
Source: frmSplasscr.frm; DestDir: {app}
Source: frmSplasscr.frx; DestDir: {app}
Source: Module1.bas; DestDir: {app}
Source: Project1.vbw; DestDir: {app}
Source: Route_management.mdb; DestDir: {app}

[Icons]
Name: {group}\Distribution Management; Filename: {app}\Distribution_Management.exe
Name: {group}\Uninstall Distribution Management; Filename: {uninstallexe}

check the table's properties before you try to remove it. it may be read only, thus not able to be deleted.

sounds like the access DB may be copying over the the second machine as a readonly file???


also sorry, by why the hell does your setup copy all the VB project files?? arent you compiling the program into an EXE???

dglienna,

Are you talking about checking the properties on the target computer? How do you do that? There is no Access on the target computer. Can you change the properties?

Kleinma,

(1) How do I copy it over as NOT a read only file? It's not a read-only file on the source computer. I didn't change it any.

(2) The instructions given to me in a previous post were to specify all the files. I believe you were in that post (not your instruction, though.)

Quote:

---

Originally posted by projecttoday
dglienna,

Are you talking about checking the properties on the target computer? How do you do that? There is no Access on the target computer. Can you change the properties?

Kleinma,

(1) How do I copy it over as NOT a read only file? It's not a read-only file on the source computer. I didn't change it any.

(2) The instructions given to me in a previous post were to specify all the files. I believe you were in that post (not your instruction, though.)

---

lol, well whoever told you all the files, i dont think they meant all the project files, just the exe and any dependancy files like DLLs or OCX, including your forms and modules means you are including all the source code for your app

as far as seeing if the DB is readonly, just right click on it and go to properties and it will tell you

also do you get a specific error message when you try to write to the DB?

It is not a read-only file. I checked. Okay, I'm changing my script. Another thing: apparently I'm not ending my program correctly. That is probably the reason I can't delete it, it's still open (my bad).

The error on the other machine just says "Errors occurred". (Not much help.) I am also using ADO.

Anyway, if you could help me fill in the missing pieces of the script that would be nice. Here's the latest version, I'm due over there right now!


[Setup]
AppName=Distribution Management
AppVerName=Distribution Management
DefaultDirName={pf}\Distribution Management
DefaultGroupName=Distribution Management
UninstallDisplayIcon={app}\Distribution_Management.exe
Compression=lzma
SolidCompression=yes

[Files]
Source: Distribution_Management.exe; DestDir: {app}
Source: adenamsm.bmp; DestDir: {app}
Source: Route_management.mdb; DestDir: {app}

[Icons]
Name: {group}\Distribution Management; Filename: {app}\Distribution_Management.exe
Name: {group}\Uninstall Distribution Management; Filename: {uninstallexe}

well for 1 thing you arent including the VB runtimes or MDAC in your installation

these are essential to running a VB exe on a machine that doesnt have VB or OFFICE installed, especially a windows 98 machine

you can download both at microsofts website, but if you are "due over there right now" then unfortunatly, you are not ready to go with this thing... you might want to bookmark www.hotjobs.com :D

projecttoday,

I think kleinma is right, your in over your head. Don't take offense to this but..You don't seem to understand what your doing. It also doesn't seem like you've read any of the innosetup documentation.

My suggestion to you is to use a freeware program call "**********". ********** will parse your vb project file and create a innosetup script file for you. It doesn't always get everything you need, but it'll give you a good head start.

You can find ********** here:
http://www.***********/**********.html

yeah please dont take my post as offense either... we are all here to help, and if you had more time we could probably help you out to get things working... but to be posting trying to figure out how to get the easiest of setups working when you are supposed to be there already with the final product, that is no good.

I mean, even when I compile a package, I still test it several times under different conditions to make sure it will work correctly.

You misunderstood. I had a meeting. That's all. The project isn't due.