Troy,

Well, another shot in the dark: do you have timer running?

Do you have grid on your form? We experienced some unwanted behavior with grid and Report Form command, when not correct alias have been selected.

Also you may close these tables somewhere in a code bellow.

>Nadya,
>Thanks for the advice. An error being thrown was my first inclination as well but I'm afraid that is not the case.
>
>Yes, I am sure I can spend more time on this and get it to work. However, this is such strange behavior that it has shaken my faith in VFP. So I can sleep at night I just need some kind of explanation on why it would behave this way. When I step through the code- I can watch the tables open in the view window perfectly. If I do not step through the code, they do not open.
>
>What could a trace window change environmentally?
>
>Thanks again,
>
>Troy
>
>
>> Hi Troy,
>
>> What does ? on('error') return? You may have your own Error Handler, which
>>doesn't show the errors on these commands. I also think, that instead of plain
>>use better use wrapper function. This is my wrapper function for the use
>>command:
>
>>>Got some old code I just inherited. I'm running it in VFP6. It's in a prg- no database containers, no data buffering and no private data sessions.
>>>
>>>It has some USE statements:
>>>USE DBFS\MIR_99 IN 0
>>>USE DBFS\FAC_INFO IN 0
>>>USE DBFS\SIZETYPE IN 0
>>>
>>>Now the weird part. If I put a break point or a SUSPEND in before the USE
>>> commands, then they work perfectly. On the other hand, if I don't put a
>>> break point in or I suspend immediately after the USE statements, then the
>>>tables do not get USED which causes an error later.
>>>
>>>I've never seen anything like this before.
>>>
>>>I sure would appreciate any insight on why VFP would behave this way.
>>>
>>>Thanks in advance.
>>>
>>>Troy