|
-
Dec 13th, 1999, 09:11 PM
#4
Thread Starter
Lively Member
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?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|