My company is in the process of upgrading everyone to Access 2007. Since my machine was upgraded I've been highly frustrated with an apparent random behaviour byAccess that I can't understand. It involves databases that I created in Access 2002 (i.e. *.mdb files).
What happens is when I open a form that has the border style property set to 'Dialog', Access 2007 is correctly preserving the size of the form itself (i.e. if you look in the properties box, the form's width and height are correct) but Access is not remembering the size of the window the form is to be displayed in. Consequenly my form opens much bigger than they're supposed to (nearly taking up the entire workspace inside Access) and all of the controls on the form are in the upper left corner of the window. I'll switch to design view and re-size the window, save the form, and things will be fine for 'a while.' But then a few days later, the window size blows up again! Ug! I have lots of people you use the databases/forms that I've created and they're complaining about this behaviour, too.
Is there some new fuctionality or form property in Access 2007 that controls this behaviour? Is this a know bug with Access 2007? Any help would be appreciated.
Thanks,
sphinney
What happens is when I open a form that has the border style property set to 'Dialog', Access 2007 is correctly preserving the size of the form itself (i.e. if you look in the properties box, the form's width and height are correct) but Access is not remembering the size of the window the form is to be displayed in. Consequenly my form opens much bigger than they're supposed to (nearly taking up the entire workspace inside Access) and all of the controls on the form are in the upper left corner of the window. I'll switch to design view and re-size the window, save the form, and things will be fine for 'a while.' But then a few days later, the window size blows up again! Ug! I have lots of people you use the databases/forms that I've created and they're complaining about this behaviour, too.
Is there some new fuctionality or form property in Access 2007 that controls this behaviour? Is this a know bug with Access 2007? Any help would be appreciated.
Thanks,
sphinney
Comment