PDW Blues =[

[JohnAtWork]

First off, the PDW seems to work without a hitch; I package into the .CAB, and deploy to the internet. No problem.

I've been on other machines, and ran the Setup program, no problem.

However, when I try and run the actual executable, I get the following:

CLICKME.EXE caused an invalid page fault in module OLE32.DLL at ...


Now I've included OLE32.DLL in my deployment (I think it's one of the standard seven programs, actually) but it still fails.

Is there something that is possibly in my actualy VB code that would cause it to install successfully in the development environment, yet fail on the end-user's machine?

Any information would be extremely helpful.
P.S. I can post the application here, since it's very small, if that would help.

[Aaron Young]

I think it would be useful to see some of the code, sometimes the type of optimization used when compiling the Project can cause unpleasent side-effects.

------------------
Aaron Young
Analyst Programmer
aarony@redwingsoftware.com
adyoung@win.bright.net

[Serge]

Also, according to Microsoft, you should not install windows core files (Click here to see the list (http://www.veritest.com/ftp/core(f).htm). Ole32.dll is a windows core file and the best way to have it in sync with all the other programs, install Microsoft Data Access Components (MDAC) (http://www.microsoft.com/data/download_21242023.htm)

Regards,

------------------

Serge

Software Developer
Serge_Dymkov@vertexinc.com
Access8484@aol.com
ICQ#: 51055819 (http://www.icq.com/51055819)

[JohnAtWork]

Here's the code... there's a few other things (unloads and whatnot) but this is the button that causes the fault.

Private Sub cmdInstall_Click(Index As Integer)
Dim fs As Object
Dim objDaughter As Object
Dim strActiveXControl As String
Dim strDatabase As String
Dim strDBDest As String

strDBDest = "C:\My Documents\Purchasing\Purchasing.mdb"

'Sets fs as a FileSystemObject to be manipulated
Set fs = CreateObject("Scripting.FileSystemObject")

If fs.folderexists("C:\Purchasing") = False Then
Set objDaughter = fs.CreateFolder("C:\Purchasing")
End If

strDatabase = "M:\Users\Common\AccessApps\AdminOnly\Purchasing.mdb"

FileCopy strDatabase, strDBDest
strDBDest = "C:\Purchasing\HorzMRP.mdb"
strDatabase = "M:\Users\Common\AccessApps\AdminOnly\HorzMRP.mdb"
FileCopy strDatabase, strDBDest
'fs.CopyFile strActiveXControl, strOCXDest

MsgBox "Installation has been completed. This application has been installed to C:\Purchasing\Purchasing.mdb", vbOKOnly, "Symbol Technologies, Inc."
Unload Me
End Sub


Serge: I have MDAC 2.1 on my machine currently; how would these files alleviate the problem related to the OLE32.DLL error?

Aaron: I'm compiling to Native Code, no optimization. (this is designed to be a patch program, in order to update the front-end application on a universal basis... there's code in the db that disallows a user to open if outdated....) Would P-Code be better?

[Serge]

Ahhhhhh, I know exactly why it happens. You should include scrrun.dll, since you're using FileSystem object.

------------------

Serge

Software Developer
Serge_Dymkov@vertexinc.com
Access8484@aol.com
ICQ#: 51055819 (http://www.icq.com/51055819)

[JohnAtWork]

Serge, I love you, and would like to find you a woman to bear your children.

Failing that, my abject thanks will hopefully be enough :)