Really Strange FoxPro Behavior

[toddsevans]

Something very strange is happening when I use SELECT...

Here is a portion of the code:

*******************************************************
SELECT deduc
SET FILTER TO deduc.loan_no = ALLTRIM(macct1)
GOTO TOP
WAIT ALIAS() WINDOW
DO WHILE !EOF()
WAIT ALIAS()WINDOW
*******************************************************

The first WAIT WINDOW returns deduc as you would expect

The second WAIT WINDOW returns borrower which is another table I have in the data environment.

I have tried USED() and AUSED() to determine that there is a table in use and that deduc is in fact open.

I cannot figure out how borrower is becoming the currently selected table.

Help!!!

 

[mspratt]

Hi toddsevans,

DO WHILE !EOF()
WAIT ALIAS() WINDOW

You need to post ALL of the code. What is a DO WHILE doing without an ENDDO. Off the top of my head I can't recall which ones, but I think there are VFP commands that implicitly change the work area.

Regards,

Mike

 

[baltman]

I assume you're sure there's nothing going on in between that might be changing the workspace, including any error routines?

Brian

 

[toddsevans]

There is a huge amount of code but I really think that all you need is this piece. Of course there is an ENDDO but the problem presents itself long before you ever reach it.

 

[toddsevans]

I have discovered that if I take out all the WAIT WINDOWS the code executes properly.

Strange that WAIT WINDOW would change the currently selected database.

 

[toddsevans]

Even a WAIT NOWAIT command causes this strange behavior

 

[Mike Lewis]

Todd,

Try setting a breakpoint to fire when ALIAS('deduc') changes.

Mike


Mike Lewis
Edinburgh, Scotland

My Visual Foxpro web site:

http://www.ml-consult.demon.co.uk

My Crystal Reports web site:

http://www.ml-crystal.com