Help! with application won't run

[slharman1]

I have my app completed, it's in the format DB, I have full menus disabled and unchecked show navigation. When I open the FE from my home computer and connect to the BE on my server at work everything works as it should. When I get to work and open the FE on workstation and try to connect to the same BE I get "The expression ON Click you entered as the event property setting produced the following error: Return without GoSub". IT is an exact copy of the FE on my home computer. What the heck is the problem?!! The on click is setting the var db to current .DB I can't figure it out.

 

[slharman1]

Looking further, I am getting "your network access was interrupted, re-open the database and try again"
One thing I forgot to mention is that I am sharing the back end with two different applications, the job tracking app and the plant management app. I am not sure if that is okay or not.

 

[jdraw]

Insufficient info. You could post copies of your FE and BE for readers to review and provide feedback. Remove any confidential info.

 

[arnelgp]

it can be many, what language did you use on building your app?
what language do you have at work?

 

[slharman1]

it can be many, what language did you use on building your app?
what language do you have at work?

Both english access 2016
What gets me is my intensive app works in both places but not the smaller one, they do share a BE though.

 

[mike60smart]

On your Work PC create a Blank New Database.

Then do an Import from the FE database.

Relink to the BE and you should be OK

 

[CJ_London]

One thing I forgot to mention is that I am sharing the back end with two different applications

to answer the question, it is not a problem for two different 'app FE's' to use the same backend. From the back end's perspective, it is no different from two different users accessing the backend whilst using the same app (local copy of the FE on each users computer of course)

 

[slharman1]

On your Work PC create a Blank New Database.

Then do an Import from the FE database.

Relink to the BE and you should be OK

Worked like a charm Thanks!

 

[MajP]

May find this useful.

Setting Database default paths

It really wasn't a big deal. I don't expect to be "spoon fed" with this stuff. Sometimes you just have to get in there and sort it! It was the modules that got me. I didn't realise until I got into the code that they were required. Not to worry though. It's a good piece of code.

www.access-programmers.co.uk

 

[mike60smart]

Worked like a charm Thanks!

Glad to help

 

[slharman1]

If relinking worked, then the problem is most likely that you are using mapped drives and the two computers are not using identical mapping to the server. The best solution for environments where this is common is that rather than using a mapped drive, use the actuall UNC name of the server. That will ensure that the FE works from all computers on the network.

So how do I put that into the linked table manager, I don't see where I can put the UNC into the linked table manager.

 

[mike60smart]

No you would put it in the shortcut on the Users desktop that Opens the FE

 

[slharman1]

No you would put it in the shortcut on the Users desktop that Opens the FE

The front end is on the user's desktop, they just click it and it should open the front end located on the physical drive and connect to the BE on the server.

 

[slharman1]

In the relink dialog, instead of choosing a drive, type in the full path to the server starting with the two slashes.

Ahh..yes I didn't think about putting it in that.
Thank you

 

[slharman1]

You're welcome.

Now, when you redistribute the FE, the links will work on all computers.

Yes, Thanks Again Pat!

 

[gemma-the-husky]

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.

 

[Gasman]

No you would put it in the shortcut on the Users desktop that Opens the FE

Could you please explain how to do that Mike?

 

[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.