Opening front end batabase with Runtime

[Cheryl R]

I have searched everywhere for this answer and am just stumped. I will try to simplify my problem and hope you guys can help me.

I have created a database and have split it into front and back ends. I have also created a user table where I have saved user logins and this should determine which switchboard opens for that user.

On the user's machine, I am using runtime to open the front-end batabase (Access is not installed on that machine). All that appears is a blank screen with a few adobe buttons at the top.

To try to correct this problem, I went into the front-end database options and set the Display Form to Main Switchboard (mine). This will allow the database to open but shows the user only my switchboard, seemingly overriding the code to open the user's listed switchboard. If I leave this option as None, then the screen is blank.



My questions is- Do I have to have a front-end for each user? I am sure there is a simple solution but I am missing it somehow.

Thank you in advance for your help.

Cheryl

[Beetle]

Do I have to have a front-end for each user?

Yes. Unless you're a fan of corruption, which is what you'll get if you let multiple users share the same front end.

Your problem could be a Trusted Location issue. This becomes a bit of a catch 22 with the Runtime because the file needs to be in a Trusted location in order to function properly, but there is no way to set a Trusted location within the Runtime.

All is not lost however, because you can do it with a (relatively) simple Registry Setting.

[Cheryl R]

Thank you, Sean.
One follow-up if you don't mind. I plan to have several technicians (only 6 or 7) using the same front-end as they will all be doing the same tasks (only need to have one form). You mention corruption as if that is something that could happen to ME (lol) and I am afraid I am heading in the wrong direction. Is there a better way to create that form rather than using access with runtime?

[Beetle]

I plan to have several technicians (only 6 or 7) using the same front-end as they will all be doing the same tasks

Every user should have their own copy of the front end, period. Multiple users sharing the same front end is probably the most often referenced cause of corruption in multi-user Access applications.

Is there a better way to create that form rather than using access with runtime?

Not sure I understand this part of your post. Creating a form has nothing to do with whether or not you use the Runtime. If you need to run the application on a machine that does not have MS Access installed, then you use the Runtime version. Whether the application has one form or a hundred forms has nothing to do with that.