Hi Rick,

Me again. Tried the download and I got all of the way through the rebuild and so a big "yeah". But then when I tried to run the program, something went goofy with some of the screens. So I reloaded a copy of the project from backup and tried again. This time I got errors again ("Invalid file descriptor") and then FPW bombed out with an internal consistency error. I tried it a number of times and it seems to be bombing when a PACK operation is performed on some table. I don't know if it has anything to do with a fairly long path to the source file or the fact that FP likes to use abbreviations for pathing but I could always try moving the source files into the project directory (they are "common" screens so that's why they are not with the project). The source path is (as FP renders it when running genscrnx):

d:\..\fpd26\common\screens\_6767997.dbf

The last number obviously is a temp file created by Genscrnx. I also tried slowing down overall genscrnx exection (in case it was that) by just putting a WAIT WINDOW "Please wait..." TIMEOUT 1 at the top of Genscrnx.

Any other suggestions or do I move this all to an old Win98 machine and try it from there.

Thx.
Albert

>Albert,
>Go to http://mmfudg.lansing.com/tips_etc.htm and in the Files section, get: GENSCRNX.ZIP [35 KB] (3/24/00) Patched for use on Faster CPUs. (Note: This has nothing to do with the FPW high speed fix, it's got to do with some temp files getting "lost".)
>
>Rick
>
>>Hi,
>>
>>I have an older app under FPW2.6 and am having trouble recompiling it now after about a year since I last touched it. Since last year, I have switched from a Win98 machine to a W2K PC. I get part way through the recompile, and at various spots, it bombs out saying it cannot find variable m.fsprout ("Food Sprout" for all I know :-) ). It is not consistent where it bombs - sometimes I get just about all the way through and it bombs so I just about cry....other times, it is only a few screens in when it happens.
>>
>>I tried opening up various screens to see if they would open etc and they do. I tried hacking the .scx to see if I could see some sort of invalid path problem (I reorganized my drives since the last PC as well - now I have all changeable code on Drive D: (ie. source files) and all program code (eg FoxProw.exe) on drive C: (to make backups easier).
>>
>>Any ideas - does Genscrnx just not work well on W2K machines?
>>
>>Albert Gostick