I have seen the behavior you speak of as the result of a printer driver, but not alot.

Another thing you may want to check. VFP5 running under NT experiences memory leaks when repeatedly using the CHRTRAN() function in such a way that the resulting string is of a different size.

Good Luck!

>Well, I think that the routine is only being run regularly on these machines. I have had to chase down problems related to printer and video drivers, but the key point here is that none of these things has changed on any of these machines in the past year or so (except mine, more RAM and different software configs almost daily). And thought I have seen problems related to drivers and such, they ususally come in the form of GPFs or Access Violations. I have never seen VFP shutdown cleanly. Thanks for your input.
>
>>Eric,
>>
>>You have to look at the 10 machines and see what is different between the ones that fail and the ones that succeed.
>>
>>OS: Are they all running the same operating system (including version - ex W95 OSR2)
>>Network: are they all on a network? the same network? are the network drivers the latest version?
>>Memory: How much physical memory
>>Diskspace: amount, configuration of ram drives,
>>Printers: are they all using the same printer: same default printers - I just spent 1.5 days chasing a problem that wound up being a printer driver: try switching to another printer. HPs and color printers seem to often be culprits.
>>Monitors: display drivers can cause problems too.
>>
>>
>>>Here's a new one. I have some code that is causing VFP to quit without warning. The code that is causing this is:
>>>
>>>CovAmountString = PADL(TRANSFORM(CovAmounts[i], "99.99X"),COLUMN_WIDTH)
>>>
>>>where CovAmounts[i] contains a Currency value
>>>($15.1523 for example)
>>>
>>>and COLUMN WIDTH is a defined constant with the value of 12
>>>
>>>this code does not generate an error, or even a Dr. Watson. It just shuts VFP down cleanly and quickly (no remnants in the task manager). But it doesn't do it every time.
>>>
>>>This code causes this in design mode, as well as in the compiled exe, and I can watch it happen in the debugger (and yes, I have verified all values)
>>>
>>>I have created many variations of the code:
>>>test1 = CovAmounts[i]
>>>intest1 = $ 16.4572
>>>test3 = TRANSFORM($ 16.4572, "99.99")
>>>test4 = TRANSFORM(intest1, "99.99")
>>>intest1 = CovAmounts[i]
>>>test2 = TRANSFORM(CovAmounts[i], "99.99")
>>>test4 = PADL(TRANSFORM(intest1, "99.99X"),12)
>>>test5 = PADL(TRANSFORM(CovAmounts[i], "99.99X"),25)
>>>test6 = PADL(TRANSFORM(CovAmounts[i], "99.99X"),6)
>>>
>>> and some of these cause the error sporadically too. The offending lines are in a tight loop, so it may not fail on the first iteration, but it usually does on one of them.
>>>
>>>Probably irrelevant but possibly related info:
>>>NT 4.0 SP 3, VFP 5.0a
>>>I recently installed Adobe PDFWriter and Distiller, but this is not present on other machines where the shutdown happens. This app is installed on 10 other machines and 3 so far have seen this behavior.
>>>
>>>
>>>What is going on? Do I need to reinstall VFP?
>>>
>>>This code is in a very important and often used routine, so any help will be greatly appreciated.