I have been developing in Access for many years and now I ran into a real brain twister.
I had been testing this form and many others in my Access 2000 app that I am developing. The form is frmShipPlan_Main which contains a subform called frmShipPlan_Sub.
There is a continuos form called frmShipPlan_Pre which shows a list of Ship Plans in the system. The form has an 'edit' button next to each line and an 'Addnew' button at the top to create a new Shipping plan. Both edit and addnew open form frmShipPlan_Main using the following code respectively:
AddNew
DoCmd.OpenForm wkFormName, , , , acFormAdd
Edit
DoCmd.OpenForm wkFormName, , , , , , Me.AutoNumID
wkFormName is set to = "frmShipPlan_Main" prior to rhese statements
I use this same model in many other parts of my application, they all work fine and even this one worked fine until recently.
It appears that this locking always occurs when I am adding a new record. A blank form appears but the app is essentially dead. Nothing can be entered. There is a button on frmShipPlan_Main which opens another form. When I press the button I get something like "Operaton Cannot be completed at this time"
Editing records works fine.
The real strangeness begins when I try to close the form and then close Access. I had to repeateldy clicking the outermost "X" button in Access and Access eventually closed. Or at least I thoght it did. My computer was running slow and when I opened the task manager the MSAccess process was using at least 50% of the CPU. Keep in mind that Access was 'closed', no Access related forms visible.
The only way I can stop the MSAccess process is to terminate the process in task manager. Otherwise it showed all indications of running forever, burning up at least 50% of the CPU at all times.
Any ideas on what is causing my runaway Access or how to fix it? I am stumped.
Start Free Trial
