>>>I have an app that runs fine on my stand-alone Windows 95 computer. However, when I run it on its eventual destination, a Windows NT server, it bombs when it gets to a combo box I am using. I fill the combo box with names from a customer table using SQL Select. Here, it loads in a blink. There, it takes a couple of minutes and then I get an error message naming my combo box and stating that the problem is an out of memory error in something called __ri_delete_customer(), Line 4, Record #6. The error # is 2005, which states that I am illegally naming a property.
>>>
>>>I assume that the __ri is referring to my referential integrity setup; I don't know where to go to look for the problem, especially since I can't replicate it here.
>>>
>>>Any ideas out there?
>>>
>>>TIA.
>>>
>>>John
>>
>>You can open 'Stored Procedures' from Project Manager's Database Tab and look for the procedure/line. I guess you used some VFP reserved name as field name.
>
>Edward:
>
>Thanks for the direction. It at least allowed me to find the source of the problem. Still can't figure it out, though--all of my RI code bombs on the NT server. No reserved words being used there that I can see. Unless you have some other idea, I will just forfeit RI (HATE TO, THOUGH!) to see if I can get this thing to run.
>
>Thanks again for the help!
>
>John

The only idea is to look at record #6 in dbc file (manually) and try to get understanding what is line 4. Also, you could 'debug' stored procedure. I'm not sure that debugger will work nicely in this case, but you could add some messageboxes inside the procedure and test it until you fine the line causing your problem.