Re: Subform Current event - workaround for multiple firing
- From: Tom van Stiphout <tom7744.no.spam@xxxxxxx>
- Date: Thu, 08 Jan 2009 07:48:14 -0700
On Thu, 8 Jan 2009 04:58:59 -0800 (PST), rightcoast@xxxxxxxxx wrote:
If you email me a zipped copy of your database (stripped down to the
essentials), I will take a look. Simply remove my .no.spam trap from
my email address.
Yes, there is one more way to battle corruption: export the documents
to text and import them into a new database. See the officially
undocumented SaveAsText and LoadFromText methods.
-Tom.
Microsoft Access MVP
Thanks for your reply. Have just tried that, but unfortunately still.
getting the same result.
If I add a second check of the values via an identical if statement,
that resolves it but obviously that shouldn't be necessary, so if
possible I'd like to get it resolved the 'proper' way. Stepping
through the code, it fires the current event twice for the first
record, then four times for each record after that. It fires the
event in immediate succession - it is not triggered by another event.
Might this be a sign of some corruption? If so, are there other
methods to resolve that in addition to decompile?
Thanks.
- References:
- Subform Current event - workaround for multiple firing
- From: rightcoast
- Re: Subform Current event - workaround for multiple firing
- From: Tom van Stiphout
- Re: Subform Current event - workaround for multiple firing
- From: rightcoast
- Subform Current event - workaround for multiple firing
- Prev by Date: Using VB to do a find/replace in a table
- Next by Date: error on new monitors
- Previous by thread: Re: Subform Current event - workaround for multiple firing
- Next by thread: Access 97 to Access 2003 conversion problem with Reports !
- Index(es):
Relevant Pages
|
