Hi MajP,Although I got rid of the setcursor and loadcursor API calls for testing, I still crashed, although less often. I would try removing all API code and see if that helps. This version posted by @arnelgp for me is even more unstable then previous versions. This crashes when I simply close the form. So I really think the culprit is API.
The main form - MainOptions, already had pop-up set and centred, together with fill screen etc...i don't see any problem with MainForm?
btw i change it to pop-up (centered).
I commented out the Load/SetCursor and compacted and compile to no avail - the same issue persists. It is not a consistent bug and, just when you think you've found the problem, it screws you up...i remove the Load cursor/Set cursor.
instead add a Transparent button overlaying on the two textbox.
Hi arnelgp,on design view, click on PlantList subform.
On Property Sheet you will see there are 2 command buttons (cmdLatin, cmdCommon).
these command buttons are "in-front" of those two fields. so you think you are clicking on
the field, but what you are clicking is the button. the buttons Back Style is Transparent.
and the Cursor On Hover property is set to Hyperlink band.
Hi arnelgp, No change, I'm afraid.on design view, click on PlantList subform.
On Property Sheet you will see there are 2 command buttons (cmdLatin, cmdCommon).
these command buttons are "in-front" of those two fields. so you think you are clicking on
the field, but what you are clicking is the button. the buttons Back Style is Transparent.
and the Cursor On Hover property is set to Hyperlink band.
MajP,The problems is on MainOptions. That was my fault I wrote MainView. I corrected it.
1. Open the MainView.
2. There is a plantlist subform on the left. Take your mouse and move it in the subform. This brings up the finger pointer.
3. Switch to design view
4. If it does not crash. Close the db and it will be locked.
Sorry that was not meant to be a fix, that was supposed to describe how to recreate the problem. I was pretty confident that it was the API call since if I did not move over the subform and went directly to design view it would not crash but crashed every time I hovered over the subform.I tried that too without any success
Was that last version stable for you? If so then you probably can readd the pointer code. If it is fixed I have no idea why.Hi MajP,
I deleted the Autoexec and opened the form from the Forms List. I don't think it's an Autoexec problem.
I will start to look at how to resolve the problem while retaining the functionality of the MainOptions form.
The version from arnelgp seems to be OK. I have been using it normally with no failures.Was that last version stable for you? If so then you probably can readd the pointer code. If it is fixed I have no idea why.
Hi arnelgp,i delete the autoexec macro where MainOptions form is being opened.
instead i use it as the Startup form.
i haven't encounter any crashing since.
for you to test.