I am in the process of converting a Jet database to ADP using SQL
Server 2000. Most of this conversation has been smooth, but now
I'm running across a problem that has me stumped. Access 2000 SP3 on
Windows 2000 Professional. I'm not in charge of the SQL server, so
I don't know its OS (presumably irrelevant). Presumably, it's been
updated with its latest service packs. With this conversion, I'm
moving everything on the VB side from DAO to ADO.
I'm running into a problem in which I'm getting error 2486: You
can't carry out this action at the present time. The error occurs on
a line that says "DoCmd.Close" (sans quotes). This is the form that
has the focus.
The form that is getting the error:
* is opened by another form using a Filter parameter
* has six subforms (two attached to tab controls)
Four of the subforms have conditional formatting on two controls each.
I've tried stepping through the code. Interestingly enough, when I
stepped through it on one occasion, the error did not occur. The
error didn't show up again for about two more runs of the form.
I can't find anywhere where it thinks a form or subform is dirty.
This form does dynamically change a subform as it opens, if necessary.
It changes the subform by referring to
Me.sf_regionalPatientList.SourceObject. This has never been a problem
in the past. When it was an MDB, it worked just beautifully. I have
no reason to believe that this is a problem now.
Googling for answers pointed me to removing the conditional formatting
(I did; no change) and importing the forms into a different .ADP file
(same result). I tried converting all my bang references to dotted
references (Me.someform.yadda instead of Me!someform.yadda). I have no
explicit references to the Forms collection (no Form!someForm!etc
references). When I try to switch to Design mode, I get the "This
action will reset the current code in break mode" error, even though
there is no apparent VB code running in the background. Exiting Access
requires going through the Task Manager, as Access refuses to exit.
I can try re-creating the subforms (a pain, but possible), but there was
no indication of corruption when I did the import into a second ADP.
I've tried the /decompile switch, just in case. No change.
One other oddity: if I click on the Access close button (to close down
everything), it looks like Access is closing down. However, the errant
form disappears and the database window and other open forms appear from
behind it. It reminds me of having two copies of Access open at the
same time, with the same database, but I absolutely do not.
To the best of my knowledge, I do not have any problems with the views or
stored procedure code on the server. I've tested them and they return
the correct results. However, if I did run a stored procedure on the
server that had a problem, or ended up in an endless loop, could this
cause Access to exhibit the behavior that it is? I would think Access
would hang until the server returned, or it popped up some error message,
but I can move around in Access and do other things (switch the tabs,
use combo boxes, etc.).
Suggestions?
Thanks,
Matt
--
---
Download my public key from http://216.99.209.78/~mattf/mjf_key.asc
