?
=?windows-1250?Q?Vladim=EDr_Cvajniga?=
There was no respond to my original post in microsoft.public.access.forms
(May 5th 2007) about a fortnight so I try it here...
—————————————————————————————————
A while ago we had a discussion about A2002 (sub)form which changes
dynamically from code (hide/unhide controls, change subfom's width, etc.).
There's a problem if I make some changes in code when the form is open: if I
save changes, A2002 saves controls positions & subform's size as well. This
is a BIG A2002 BUG and it's really annoying. Why Access forms don't behave
as Visual Basic forms? I don't want Access to change my (sub)forms' design
properties... grrrrrrr....
Somebody has recommended not to save changes when I'm in debug and/or(?)
break mode. Good idea, but sometimes I simply forget... today (May 5th 2007)
it happened
twice...
1) Do I really have to close all forms and return to database window when I
need to make changes in my "dynamic" (sub)forms?
2) Any workaround to avoid user's CtrlS on such (sub)forms? Do I really have
to add a code to Form_KeyDown events? All forms? :O
3) Does A2007 behave the same way?
4) Is there any document, official or unofficial, about how to correctly
handle code-writing in MS Access to avoid:
a) project database corruption?
b) loss of parts of project's code (which I've been experiencing for several
months - since I have switched from A97 to A2002)?
I'd appeciate a list of "situations" when I should not make any changes in
code:
a) debug
b) break
Also, I'd like to know what exactly do both debug and break in MS Access
2002. There's poor information about debug/break in A2002 help.
During last few days I've lost some parts of VBA-code mostly after I reset
the A2002 project and added new code (just after A2002 gave me some error
and I chosen "debug"). I have decompiled the project but I'm affraid I'm
still in trouble. :-(
I have never lost any part of code written in Visual Basic 6.0 but it's
quite different in MS Access. Access developers' team should definetely make
a research on what they're doing wrong in handling Access's VBA code. Access
should not allow programmers make changes in code when it may cause any
possible problem with MDB-corruption/VBA-code-loss.
If it is a problem why they don't simply store project files (forms,
reports, VBA-modules) in text files? Then, Access should all necessary stuff
from text files compile and add to MDE. In VB6 I have all the code stuff in
ASCII-files which is really safe compared to Access.
TIA
Vlado
(May 5th 2007) about a fortnight so I try it here...
—————————————————————————————————
A while ago we had a discussion about A2002 (sub)form which changes
dynamically from code (hide/unhide controls, change subfom's width, etc.).
There's a problem if I make some changes in code when the form is open: if I
save changes, A2002 saves controls positions & subform's size as well. This
is a BIG A2002 BUG and it's really annoying. Why Access forms don't behave
as Visual Basic forms? I don't want Access to change my (sub)forms' design
properties... grrrrrrr....
Somebody has recommended not to save changes when I'm in debug and/or(?)
break mode. Good idea, but sometimes I simply forget... today (May 5th 2007)
it happened
twice...
1) Do I really have to close all forms and return to database window when I
need to make changes in my "dynamic" (sub)forms?
2) Any workaround to avoid user's CtrlS on such (sub)forms? Do I really have
to add a code to Form_KeyDown events? All forms? :O
3) Does A2007 behave the same way?
4) Is there any document, official or unofficial, about how to correctly
handle code-writing in MS Access to avoid:
a) project database corruption?
b) loss of parts of project's code (which I've been experiencing for several
months - since I have switched from A97 to A2002)?
I'd appeciate a list of "situations" when I should not make any changes in
code:
a) debug
b) break
Also, I'd like to know what exactly do both debug and break in MS Access
2002. There's poor information about debug/break in A2002 help.
During last few days I've lost some parts of VBA-code mostly after I reset
the A2002 project and added new code (just after A2002 gave me some error
and I chosen "debug"). I have decompiled the project but I'm affraid I'm
still in trouble. :-(
I have never lost any part of code written in Visual Basic 6.0 but it's
quite different in MS Access. Access developers' team should definetely make
a research on what they're doing wrong in handling Access's VBA code. Access
should not allow programmers make changes in code when it may cause any
possible problem with MDB-corruption/VBA-code-loss.
If it is a problem why they don't simply store project files (forms,
reports, VBA-modules) in text files? Then, Access should all necessary stuff
from text files compile and add to MDE. In VB6 I have all the code stuff in
ASCII-files which is really safe compared to Access.
TIA
Vlado