?
=?iso-8859-1?Q?Vladim=EDr_Cvajniga?=
Is it a bug? Does Microsoft know about it?
David W. Fenton said:Turn it OFF and you'll have less corruption.
David W. Fenton said:Turn it OFF and you'll have less corruption.
David W. Fenton said:Turn it OFF and you'll have less corruption.
The problem remaine even with COMPILE ON DEMAND set to OFF.
What do you think I don't understand? I wrote I would prefer EXEs insteadof
MDBs. What kind of missunderstanding is it?
Of course I remember.That you ask this question shows that you truly *don't* understand
Access, nor why there would be no advantage at all to having an EXE.
Does that mean that I must create all tables, queries, forms,
reports & modules again? :O
Or, will de-compile be enough?
Or, import will do what I need now?
I can't imagine that I have to to re-create the whole MDB project
step-by-step. If it's true I will surely switch to Delphi!
Does that mean that I must create all tables, queries, forms,
reports & modules again? :O
Or, will de-compile be enough?
Or, import will do what I need now?
I can't imagine that I have to to re-create the whole MDB project
step-by-step. If it's true I will surely switch to Delphi!
I will have to write a letter to Microsoft to clarify the
database corruption issue. I simply can't spend time on MDB
re-creation.
I'd appreciate some rules what can be done and what cannot be done
while creating a project and debbugging it. If changes in break
mode can destroy my project then there's something wrong in
Access's concept!
Yesterday I was directed to
http://groups.google.co.uk/group/comp.databases.ms-access/browse_th
read/thread/3414643c680315b0/639b2de99404b26b?lnk=st&q=COMPILE+ON+D
EMAND+is+ON&rnum=1&hl=en#639b2de99404b26b.
It's quite important to know that Access can do such funny things.
Vladimír Cvajniga said:Yesterday I was directed to
[thread on the dangers of COMPILE ON DEMAND]
http://groups.google.co.uk/group/comp.databases.ms-access/browse_th
read/thread/3414643c680315b0/639b2de99404b26b?lnk=st&q=COMPILE+ON+D
EMAND+is+ON&rnum=1&hl=en#639b2de99404b26b.It's quite important to know that Access can do such funny things.
If you're a professional Access developer, these are the kinds of
things that you should already know, seems to me.
David W. Fenton said:Yesterday I was directed to
[thread on the dangers of COMPILE ON DEMAND]http://groups.google.co.uk/group/comp.databases.ms-access/browse_th
read/thread/3414643c680315b0/639b2de99404b26b?lnk=st&q=COMPILE+ON+D
EMAND+is+ON&rnum=1&hl=en#639b2de99404b26b.
It's quite important to know that Access can do such funny things.
If you're a professional Access developer, these are the kinds of
things that you should already know, seems to me.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.