Re: Printing under various Wins and r/t
From: Allen Browne (AllenBrowne_at_SeeSig.Invalid)
Date: 06/19/04
- Next message: Jeff Boyce: "Re: How to know if record changed in unbound form"
- Previous message: Steve Schapel: "Re: date"
- In reply to: pvp too: "Printing under various Wins and r/t"
- Next in thread: pvp too: "Re: Printing under various Wins and r/t"
- Reply: pvp too: "Re: Printing under various Wins and r/t"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 19 Jun 2004 17:38:56 +0800
There are *many* causes for this particular error. Basically, it is saying,
"I can't do what you asked for, because I have to do something else first
and I can't do that at present." Of course, the "something else" can be
anything! Here are some examples:
1. Events
What events may need to run before Access can run the report? For example,
the BeforeUpdate or LostFocus of a text box, the BeforeUpdate or AfterInsert
of a Form. You can avoid these issues by explicitly saving:
If Me.Dirty Then
Me.Dirty = False
End If
The code doesn't prevent the issue, but it does move you closer to
identifying the issue.
2. Bad filter
If you misspell a field name in a Filter or the WhereCondition of the
report, Access allows you to assign the Filter property, but it then fails
when you try to set the FilterOn to true. The message then indicates that
the previous operation (i.e. setting the Filter property) failed when the
FilterOn was attempted. This is a common issue, e.g. it also happens in
DLookup().
3. Name AutoCorrect off?
Tied to number 2, if you have not unchecked the boxes under Tools | Options
| General | Name AutoCorrect, Access may attempt to track changes to the
field names, and so you can receive the error even if you are using the
right names. For more information on this issue, see:
http://allenbrowne.com/bug-03.html
4. Unclosed objects
You can also receive the error if you have previously opened something
(form, recordset, ...) and failed to close it, or Set an object variable and
failed to dereference it by explicitly setting it to Nothing before exising
the routine where the object was declared, or by using public variables that
remain set and cause concurrency issues. Since another process is current,
the current process cannot proceed.
5. Service patches
There were bugs in JET that caused the error. When you create the runtime,
it does not automatically apply the latest patches, so you need to
explicitly run the patch for Access runtime 2002 and also for JET 4 on all t
he workstations. Expecially Jet 4! See:
http://support.microsoft.com/support/servicepacks
6. Separate runtimes
The runtimes generally include the system DLLs. Win 98/ME use different
system files than Win 2000/XP. You will probably need to install the runtime
packaging wizard on a Win98 machine, and create a separate release of the
software for Win98 than for WinXP.
If that does not solve the issue, someone may have a clue in the newsgroup:
microsoft.public.access.developers.toolkitode
-- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "pvp too" <anonymous@discussions.microsoft.com> wrote in message news:1edb301c455d4$0b11a530$a001280a@phx.gbl... > This will sound vague but I cannot get to the bottom of > this. MS support technical d/b does not give useful > answers and newsgroups do not seem to explain the message > in a way that fits the facts as known. > > I have a prog in Access 2000 runtimed by Access 2002 Dev. > There is very simple print code in this prog. Printing > reports works a treat under Windows XP under Access. > Under Windows ME and Wiundows 98 runtime, IT fails, > usually giving a message along the lines of > > "you cancelled the previous operation" > > Has anyone else come across this? This is urgent - we are > releasing this thing next Monday... > > Heeeeeeeeeeeeeeeeeeeeeeeeeeeeeelp! > > Many thanks.
- Next message: Jeff Boyce: "Re: How to know if record changed in unbound form"
- Previous message: Steve Schapel: "Re: date"
- In reply to: pvp too: "Printing under various Wins and r/t"
- Next in thread: pvp too: "Re: Printing under various Wins and r/t"
- Reply: pvp too: "Re: Printing under various Wins and r/t"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
