User-interface operation not allowed at this time. 1031

[grahamrhind]

I note that this error gives problems to others, but I'm getting it in different situations to others in other threads, so here goes:

I'm getting this error "User-interface operation not allowed at this time. 1031". This is in a VFP 6 DLL COM component being accessed by Visual Basic 6.

The error is appearing in lines starting:

USE path\database name

The program is using dbfs directly, not a cursor as in other threads. Only one database is open at a time. The program is not trying to send a dialogue or any other message to the user, nor open a report. The data is there in the right place. The database is closed after each call of the process in the dll. More worryingly, on my PC, with VFP installed, there are no errors. On the test PC without VFP, the error occurs.

Any bright ideas? Thanks in advance!

 

[alvechurchdata]

I hope you will be able to track down the problem.

I'll second that. I can't suggest anything new to try but please report back when you do crack the problem. It's been a good educational thread.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[craigber]

TRY/ENDTRY is not a debugging to. It is an exeception handling tool. Having said that...it may help you to more easily figure out what the problem really is.

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[Olaf Doschke]

Hi Graham,

true, you may narrow the area of the error with TRY..CATCH..ENDTRY better than with an ON ERROR routine. I'm really interested in the reason you'll finally find. It must be something really weird.

Bye, Olaf.

 

[grahamrhind]

I promised an update on this issue.

The problems were occurring in VFP 6. I have upgraded to VFP 9 and, without any further changes, this has resolved the issue.

Conclusion: I still cannot identify what the problem was, but upgrading does resolve it.

Graham

 

[dbMark]

Although Visual FoxPro 6.0 is referred to as the first solid and stable VFP release, it does have various quirks that were not fixed until later versions, as you can see in my thread1253-812213. As you found out, it's a good reason to upgrade. Each version keeps getting better.

dbMark