Making an executable file from VB 1

[pit75]

I'm making a little client-server VB application; so I write the server project and the client project.

Debugging and executing the application from Vb environment, doesn't give me any error...but after I've created the executable file, my c/s application doesn't work!it gives me a fatal error , and then displays this message on server application : run time error 438 (Object or property doesn't supported...etc) , and I dont' know why executing the c/s application it works, and the executable doesn't....if you have any ideas, please tell me...also if you need the code I'm using for client.

This is the code for server :

'wss = winsocket

Private Sub cmdActivate_Server()
List1.Clear

wss.RemotePort = XXXX
wss.Bind 2000, "XXX.XXX.XXX.XXX" ' this is the local machine which will work as 'server
wss.Listen
cmdActivate_Server.Enabled = False
txtServerState.Caption = "OK- waiting for client connection"

End Sub

Private Sub Exit_Click()
wss.Close
Unload Me
End Sub

Private Sub wss_Connect()
txtServerState.Caption = "Connection Enabled"
End Sub

Private Sub wss_ConnectionRequest(ByVal requestID As Long)
If wss.State <> sckClosed Then
wss.Close
End If

wss.Accept requestID
txtServerState.Caption = requestID & &quot; connected&quot;
End Sub

Private Sub wss_DataArrival(ByVal bytesTotal As Long)
Dim c_buffer As String
wss.GetData c_buffer, bytesTotal
List1.AddItem c_buffer
End Sub


Private Sub wss_Error(ByVal Number As Integer, Description As String, ByVal Scode As Long, ByVal Source As String, ByVal HelpFile As String, ByVal HelpContext As Long, CancelDisplay As Boolean)
txtStatoServer.Text = &quot;Error: &quot; & Description
End Sub

 

[chadt]

your missing files!!

Make a setup package or make sure all the required libraries (dll's...ocx's) are on the target machine.

 

[chiph]

Yes, your machine is missing the VB runtime files. Best way is to create a setup package using the pacakge & deployment wizard (PDW) or a 3rd party tool like Wise or Installshield. Since you're doing database access, make sure the latest MDAC_TYP.EXE gets included in your setup -- it has the latest ADO components in it.

Chip H.

 

[pit75]

Ok, I have made a setup package, but it doesn't work; the error messages are the saqme, but I've found this message when I develope the package : it cannot find the dependency information for FM20.DLL ........should I try to download a new version of this DLL? I'm in trouble, please help.

 

[johnwm]

See MSDN:

http://support.microsoft.com/default.aspx?kbid=224305

________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first

'People who live in windowed environments shouldn't cast pointers.'

 

[pit75]

Thanks for the tip, but it isn't helpful as I've hoped... Now I've downloaded a fixed version of FM20.DLL...but nothing works. If you have any tips, information , I'm here (in truble...)
bye!

 

[chadt]

I don't know what else to tell you......thats what is wrong.....maybe the .dll isn't being installed on the target machine.

Maybe run the setup package on a machine and then search for the file you are looking for to make sure it is there.

 

[CajunCenturion]

FM20.dll is not distributable.

There are a couple of options to deal with this. 1) Install at least one module of MS Office. FM20 is part of the office suite and installing office will install and register FM20.DLL. 2) Download from MSDN, the ActiveX Control Pad and install that on the client's machine. That will also install and register FM20.DLL.

Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[pit75]

Thank you all.
The problem was that i need to un-register first (with regedit) and re-register some of DLL's from prompt, fm20dll at first place; the packages now work properly.