>>Hi Nancy
>>
>>I am running VFP6 SP3
>>
>>I created a report using the wizard. Took a very long time to compile but once compiled I get instant access to the report. However, not much change anywhere else.
>>
>>I think the last point you brought up has merrit! What has changed in my system?
>>
>>Since last modifying my reports I have installed an HP 2000C color printer, an HP 6350 Scanjet ADF Scanner and I have networked this computer to a new one.
>>
>>One of the things that I failed to mention to this point is that during the long load time either when I am going in to modify the report or running it in my APP my USP starts beeping as though it is experiencing a power failure.
>>
>>As I mentioned earlier I have reinstalled windows, uninstalled and reinstalled VFP6 and Service Pack 3, but to no avail.
>>
>>I also took Mark Gattis's suggestion re: replacing Tag, Tag2 and Expr with ' ' in my frx.
>
>
I tried to read rest of this threat and noticed "..exe runs OK unless it's run on development machine..". Keeping this in mind I would ask :
>What's the printer driver you're using on your machine ? Do other machines use the same HP driver and run fast ? Pls temporarily remove any vendor driver and install a generic compatible HP driver that ships with win or just temporarily use no printer driver (A "generic text printer" driver if you must).
>If that doesn't make any change then let's think of other possibilities.
Another possibility - how's the size of the FOXUSER file on the development machine? Maybe a quick SET RESOURCE OFF, USE FOXUSER EXCL, DELETE FOR UPPER(NAME) = "
name of form in uppercase", PACK, USE, SET RESOURCE ON might help, since lots of data related to system preferences gets built up over time, including details on report display and frx editing details.
