Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
DataEnvironments
Message
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Miscellaneous
Thread ID:
00322871
Message ID:
00322889
Views:
23
>James - I know you want/need an answer from Kevin on this, but one thing in your message rings a bell with my experience that I thought might be useful to you...
>
>Regarding the aspect of the bizobj's getting destoyed & cursors remaining open. I've since this type "messed up" stuff too, when I setup a form that did a lot with mutliple BizObj's, got it working, then decided to change the form's primary bizobj to one on the form itself instead of Thisform.oPrimaryBizObj pointing to first page on pageframe bizobj. It was ugly... I changed the primary biz obj and the consequences seemed as if my data environments got wacky. Once I changed that primary bizobj back to where it was things got better briefly... and I shortly thereafter corrupted the whole dang adataenv.vcx anyway & had to start over with bizobj configuration shit. After redoing all that, I still seen the occaisional cursor left open with just that one form, but since they got closed eventually when the form was destroyed I could live with it.

Roxanne,

This application worked like a charm for more than a year. It wasn't until I upgraded the framework and recompiled it when things started going nuts. Unfortunately, I have a deadline of Friday to get things working. I am not sure I have time to rebuild my application. It would be nice if the cursors got closed by the bizobj everytime. If not, I am going to have to hardcode it for now. I wonder if this has anything to do with the bug in the builder corrupting the dataenvironment class?
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform