>It may not be a coding issue, but a DATA issue. I've seen this happen where a table is changed or, for the first time in forever, someone didn't enter the data in the field for gcProduct and the program can't handle it. Maybe the screen is supposed to pull the product codes from another table that didn't get loaded on the new machine, or the that table was set up incorrectly.
>
>I would start by looking at your databases, then ensure that you are entering your test data the same way it is entered in production.

Thanks much for the reply. But, this is a networked system and workstations with Win 98 and Win 95 are ok. It is the new/OS upgraded Win NT and Win 2000 machines that blow up. Also at the point in the code where the crash occurs no tables are being accessed, it is only dealing with string variables.