Help! with application won't run (1 Viewer)

[mike60smart]

Hi Gasman
My error. It is as Pat describes.

 

[slharman1]

Just a further thought. You ought to have code in your front end that maintains a persistent connection to the back end. This will speed up performance for multiple concurrent users, and may help protect against network dropouts.

Can you expand on this please

 

[gemma-the-husky]

Can you expand on this please

When a user needs to read from an access table stored on a server (split database), a PC has to negotiate a connection to that server. If other users are using the database, then this can add a few seconds per table. If you have a database with say 10 tables, you might find that it can take 20-30seconds before a menu appears for a new user if the database is already in use.

To get around this we often add a hidden form or a hidden recordset connecting to a "dummy" table. This keeps the connection to the data database permanent or persistent, and the connection doesn't have to be negotiated each time. If the connections are being discarded by the server after a timeout period, this may also help with "network access interrupted" issue, although I am not sure about that.

 

[Pat Hartman]

Create a new table in the BE. Link to that table. Create a form bound to that table. If you have a login form, open the new form and hide it by changing its visible property to No as the last step before opening your main form. If you don't have a login form, you can use your Switchboard or whatever Menu form you use to give a framework to the application.

 

[slharman1]

When a user needs to read from an access table stored on a server (split database), a PC has to negotiate a connection to that server. If other users are using the database, then this can add a few seconds per table. If you have a database with say 10 tables, you might find that it can take 20-30seconds before a menu appears for a new user if the database is already in use.

To get around this we often add a hidden form or a hidden recordset connecting to a "dummy" table. This keeps the connection to the data database permanent or persistent, and the connection doesn't have to be negotiated each time. If the connections are being discarded by the server after a timeout period, this may also help with "network access interrupted" issue, although I am not sure about that.

Thanks