VB6 application crashing on win2k and XP

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

it some times crahes when i use a dll i have made in another program. i.e i
have made a dll for acting like a server and client so it sends and receives
message from other servers. when i call it from a program it gives me that
vb6 error and you must close now. it says according to that system cannot
read memory address.
plz can any one gives me a guess what could it be?
.

Relevant Pages

  • Re: Please help
    ... Unable to open the Server service. ... DLL files to display messages from a remote computer. ... The NVIDIA Driver Helper Service service hung on starting. ... have the necessary registry information or message DLL ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Win2k3 SP1 error: New transaction cannot enlist in the specifi
    ... What we came upon was the fact that Windows Server 2003 requires roles to ... Do you use SQL Username and password, or SSPI to logon to the database (if ... >> This dll supports transactions, but does not initiate transaction calls. ...
    (microsoft.public.windows.server.general)
  • Re: DCOM Surrogates
    ... > believed it was possible to create a remote-server dll where I did not ... you're server has to be instantiated in a runnable process. ... but I am quite excited about this technology and what it ... then have to change the main app to accomodate it. ...
    (comp.lang.pascal.delphi.misc)
  • Re: screen scrape / remote manipulation
    ... Functionally a dll is no different from an .exe in terms of spying ... The other option is to install software capable of monitoring TCP/IP port ... connection is established between the dll (on the client) and the server, ...
    (microsoft.public.windowsxp.general)
  • Re: VB6 Winsock action on Server
    ... my usage of server app I meant the app on the server ... It is this piece 'dll' that i ... to delegate each request to a separate instance ... back to your Clients directly from *inside* the WorkerThreads, ...
    (microsoft.public.vb.general.discussion)