I have a Visual Basic DLL, that I created that in turn has an Activex control. This is called from VFP, effectively as a subroutine, to do some tasks, and create a CSV file, that is then imported into a table. So the VB modules does nothing with FoxPro tables. This is first imte I ever had to do something like, this, but it's been working in test mode for a few months.

All of a sudden, when I run it at the client, it's begun to crash the VFP application. I don't have any development system installed on the clients machine, so I can't run it in debug mode there.

The code is basically like this

oMyVBObject = CREATEOBJECT("xxxxVFP.Fetch") && this is my DLL

... create a CSV file and pass it to the method in the DLL

oMyVBObject.ReadCSV("my1.csv"+CHR(0),"my2.csv"+CHR(0), 'paramter string' )

... the ReadCSV method, reads each line in the my1.csv, passes data line by line from it to the ActiveX control, and then writes out results to the my2.csv

..return from the DLL

... process the my2.csv file, which has been created by the DLL code

RELEASE oMyVBObject

Since it seems to create and process the CSV files, it looks like it crashes the EXE when the RELEASE gets executed, I'm going to add some trace messages to see.