SQL Server Bit Fields & Bound Form Fields Incompatibility

[ESquared]

I did finally find a workaround, although I don't know how globally thi
can be applied, as I've only used it on one form so far. I sure hope i
helps someone avoid some frustration.

Access (sometimes?) runs certain events in this order when you click o
the checkbox:
Control_GotFocus
Form_BeforeUpdate
Form_BeforeUpdate (yes, twice, and in certain instances all the primar
key autonumber columns have sequential values starting at 1 the firs
time, then have their proper server-side values the second time, bu
that's not related to this issue.)
Control_BeforeUpdate
Chb_AfterUpdate
Control_Click

The crash always happens immediately after one of the form_beforeupdat
events (and before the control's beforeupdate event). If both of thos
beforeupdates cancelled then the crash does not occur. So my workaroun
was surprisingly simple:

Declare a global boolean, something like gfPreventUpdate.
* In the control's GotFocus event:
gfPreventUpdate = True
* In the form's BeforeUpdate event:
Cancel = gfPreventUpdate
* In the control's BeforeUpdate, AfterUpdate, or Click event (whicheve
is convenient for you):
gfPreventUpdate = False

Eri

 

[aaron.kempf]

I agree

Microsoft is a bunch of assholes that WONT FIX BUGS IN THEIR SOFTWARE

SCREW YOU MICROSOFT

I think that we should contact Ralph Nader and ask for a Class Action
Lawsuit.

i mean-- those assholes; I've been bithcing about this stuff for years

the only problem that Microsoft has is that they're not FORTHCOMING and
HONEST about bugs.

We need an independent company to keep track of all of these Access
bugs and Force microsoft to fix them.

Oops, I'm sorry did i make some FAT LAZY PROJECT MANAGER AT MICROSOFT
SAD TO READ THIS??!!??

GET OFF YOUR ASS AND START FIXING BUGS MICROSOFT

IN ___THIS____ VERSION OF OFFICE YOU ASSHOLES

 

[ESquared]

There also needs to be a gfPreventUpdate = False in th
Control_LostFocus event because someone could tab to the control an
away from it without using it. Also, if any weird update-preventin
situation arises, consider whether some other event also needs to hav
this flag set to false to provide normal function

 

[aaron.kempf]

WHY WONT MICROSOFT START TREATING US SERIOUSLY?

FIX YOUR BUGS MICROSOFT

I've been screaming bloody fucking murder about this for years now