AllowBypassKey Property

  • Thread starter Thread starter Keith
  • Start date Start date
It is a feature for developers, and IMO Microsoft was correct to implement
it as currently designed. I would imagine that Microsoft didn't want to
deal with support headaches caused by users not understanding its purpose
and use and subsequently locking themselves out of a database.
 
"Built in" to what?

All such properties are handled by the underlying database engine, MS
Jet. AllowBypassKey is not relevant to MS Jet, so it's no surprise that
it is not built in to Jet.

But Access could certainly create it automagically if it wanted to. I
can't think of any good reason why it shouldn't.

HTH,
TC
 
Sorry Keith, I didn't mean a lecturing tone in: "the underlying
database engine MS Jet". I assumed that it was any old Keith, I didn't
realize that it was you at first. But what I said stands, there's no
way the Jet property manager would want to create that property unless
it was asked to; but I can't see why Access couldn't create it.

Cheers,
TC
 
Donno, but this was the microsoft standard at
the time. Unused properties, like unused registry
entries, were not created unless required.

BTW, notice that the system is also expandable -
you can set the SubDataSheetName to [none]
on an Access97 table, even though that
property was not invented until later.

(david)
 
TC said:
Sorry Keith, I didn't mean a lecturing tone in: "the underlying
database engine MS Jet". I assumed that it was any old Keith, I didn't
realize that it was you at first.
Click to expand...

No problem TC. I thought I was "any old ..." too ;-)
But what I said stands, there's no
way the Jet property manager would want to create that property unless
it was asked to; but I can't see why Access couldn't create it.
Click to expand...
That's kind of what I meant. The code to create and set it is in the help
so why not make it a selectable option? I do take Paul's point that it
might turn into a support headache with people locking themselves out left,
right and centre.

Regards,
Keith.
 
I remember some time ago, checking out what happens to deleted
properties. I concluded that the /names/ of deleted properties, were
retained forever, even after they had been deleted, & even after a
compact!

Of course, this might have been an unpredictable side-effect of Jet not
initializing unused portions of the mdb file, to zero. Instead, any old
rubbish might be in there. But I did do quite a few tests, & the
deleted property names never disappeared from the file, even after
repeated compacts.

So maybe it's not such a good idea to create that property,
"TEMP_FIX_FOR_STUPID_USER_JOHN_SMITH" :-)

TC
 
Back
Top