If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Form stays with transparent background
Access 2007 on Vista
I am using a form to act as a message box to seek the users patience while data connections are completed. The connecting process runs about 34 seconds on the current hardware. The form is opened with a DoCmd.OpenForm, but is only partially rendered and the background remains transparent. After the completion of significant later code, the form finally is fully presented, but way too late to be either beneficial or professional. How can the complete form opening be forced before program moves on to processing more code? Inserting intentional delay routines is obviously never a logical wish. Might there be a trick I am missing here? Thanks as Always...... Justin |
#2
|
|||
|
|||
Form stays with transparent background
We do use a small delay when we need to.
You can also use DoEvents to allow access to run other processes before it returns to your code. If neither of these work for you, there needs to be a way to make the form finish loading before the connection code starts to run. Untested idea: Maybe a call to do something simple in the form's current event before you call the connection code. Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia "The Grape Hunter" wrote in message ... Access 2007 on Vista I am using a form to act as a message box to seek the users patience while data connections are completed. The connecting process runs about 34 seconds on the current hardware. The form is opened with a DoCmd.OpenForm, but is only partially rendered and the background remains transparent. After the completion of significant later code, the form finally is fully presented, but way too late to be either beneficial or professional. How can the complete form opening be forced before program moves on to processing more code? Inserting intentional delay routines is obviously never a logical wish. Might there be a trick I am missing here? Thanks as Always...... Justin |
#3
|
|||
|
|||
Form stays with transparent background
Justin
If your form is bound to a recordset that only exists after the connection is completed, I could see that form taking a long time! What about the idea of opening the form unbound, then binding it to the recordset after the connection process finishes? Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "The Grape Hunter" wrote in message ... Access 2007 on Vista I am using a form to act as a message box to seek the users patience while data connections are completed. The connecting process runs about 34 seconds on the current hardware. The form is opened with a DoCmd.OpenForm, but is only partially rendered and the background remains transparent. After the completion of significant later code, the form finally is fully presented, but way too late to be either beneficial or professional. How can the complete form opening be forced before program moves on to processing more code? Inserting intentional delay routines is obviously never a logical wish. Might there be a trick I am missing here? Thanks as Always...... Justin |
#4
|
|||
|
|||
Form stays with transparent background
I of course was assuming that the form was not bound to the recordset you
were trying to open after connecting. Thanks Jeff Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia "Jeff Boyce" wrote in message ... Justin If your form is bound to a recordset that only exists after the connection is completed, I could see that form taking a long time! What about the idea of opening the form unbound, then binding it to the recordset after the connection process finishes? Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "The Grape Hunter" wrote in message ... Access 2007 on Vista I am using a form to act as a message box to seek the users patience while data connections are completed. The connecting process runs about 34 seconds on the current hardware. The form is opened with a DoCmd.OpenForm, but is only partially rendered and the background remains transparent. After the completion of significant later code, the form finally is fully presented, but way too late to be either beneficial or professional. How can the complete form opening be forced before program moves on to processing more code? Inserting intentional delay routines is obviously never a logical wish. Might there be a trick I am missing here? Thanks as Always...... Justin |
#5
|
|||
|
|||
Form stays with transparent background
.... and it may not be ... I'm just trying to rule out possibilities ...
Jeff "Jeanette Cunningham" wrote in message ... I of course was assuming that the form was not bound to the recordset you were trying to open after connecting. Thanks Jeff Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia "Jeff Boyce" wrote in message ... Justin If your form is bound to a recordset that only exists after the connection is completed, I could see that form taking a long time! What about the idea of opening the form unbound, then binding it to the recordset after the connection process finishes? Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "The Grape Hunter" wrote in message ... Access 2007 on Vista I am using a form to act as a message box to seek the users patience while data connections are completed. The connecting process runs about 34 seconds on the current hardware. The form is opened with a DoCmd.OpenForm, but is only partially rendered and the background remains transparent. After the completion of significant later code, the form finally is fully presented, but way too late to be either beneficial or professional. How can the complete form opening be forced before program moves on to processing more code? Inserting intentional delay routines is obviously never a logical wish. Might there be a trick I am missing here? Thanks as Always...... Justin |
Thread Tools | |
Display Modes | |
|
|