V
Vladimír Cvajniga
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 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?
3) Does A2007 behave the same way?
TIA
Vlado
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 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?
3) Does A2007 behave the same way?
TIA
Vlado