For Rus: Shared Library do you mean Serial Lib ( SysLibFind )? If no, I don't use shared Library. serial Port is closed, thats for sure i've tested this a long time. I don't use database either.
For Aaron: I would use POSE but I have serial comm and I didn't find a way to simulate modem call with POSE so I can't get to the point where the error ocurs, you see (I'll try to explain shortly) I communicate via modem with a server that sends me some data 5 string containing client info then 1 to 25 lines containing data ( around 50 char lenght ) But If I use POSE I can't make it to call the server (since it's on the same computer and that I never found how to use POSE to make comm over serial cable) so it never receive the 30 lines of data. ( it waits for the comm (MdmDial) to finish but it never) What make me think it could be memory management problem is that If I use pose and comment out every line of COMM ( SerSend, SerReceive...) ( So I never fill the 25 lines list and 5 labels ) It doesn't crash at the end of my apps. > What might be happening could be several things. Check to see if all > of your shared libraries are being closed properly in your AppStop > function. Also, check to see if you're shutting down your serial port > properly...it doesn't usually cause that particular error (usually it > keeps you from hotsyncing properly, sending data in other apps via serial, > etc.)...make sure you're closing your databases properly. > > -Rus get yourself a copy of POSE, install a debug rom.. chances are, you may be doing something with a NULL pointer on your exit? i can think of a number of ways to crash your program on exit, and the most common one is using a handle incorrectly or dealing with a null pointer cheers // az [EMAIL PROTECTED] -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
