S
Scott Pendleton, Tulsa, OK
If you have a procedure that, multiple times in succession, opens a form as
acDialog, then you will get a low memory warning and the fonts and colors on
your forms will get weird.
I was using a custom form to get data input from users. I opened the form as
acDialog so processing would wait for the user input. Pow!
Workaround was to use the InputBox function in place of my user form.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...32a6&dg=microsoft.public.office.developer.vba
acDialog, then you will get a low memory warning and the fonts and colors on
your forms will get weird.
I was using a custom form to get data input from users. I opened the form as
acDialog so processing would wait for the user input. Pow!
Workaround was to use the InputBox function in place of my user form.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...32a6&dg=microsoft.public.office.developer.vba