uploading FE and BE

[Sheba]

Can someone help me please? I need to place my FE and BE on the server for testing. What information do I need to provide IT with beside the file names?

[June7]

Users need read and write permissions to the folder that has the backend file.

Are you linking the frontend to backend with UNC pathing?

[orange]

Why is FE being put on server? Each user should have copy of FE on their PC.

[Missinglinq]

...Each user should have copy of FE on their PC...

The 'swinging cat' is absolutely right; this simply has to be done! The fact that you're talking about placing the Front End on the server would indicate that you plan on letting the users access the file from there, and having multiple users sharing a single Front End, on a network drive, is the sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior!

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past eight years have seen literally dozens and dozens of reports of split databases, using links to a single Front End, causing these kinds of problems, as well as massive data loss! The really insidious thing is that this kind of setup can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

Linq ;0)>

[Sheba]

Hi June7, no I'm not linking the FE and BE with UNC pathing. This would be my first database deployment and I've never done this pathing before. I've only used the Link table manager...

[Sheba]

Hi Orange, yes each user is going to have a copy of the FE on their laptops but I thought that in addition to that, the FE would still be on the server...? I guess not

[Sheba]

hey Linq I agree with you. Each user will have a copy on their computer.

Thanks

[June7]

You need a master of the front end to do design edits. Where you store the master is up to you. I have a folder with limited permissions that holds the master. Revision is saved to another folder with no limitations so it is available to users and I can continue edits without disrupting users. I have code in the db that automatically copies itself to the users C: root when there is a revision. Review https://www.accessforums.net/code-re...31/index2.html

It is best to use UNC pathing otherwise every user will require the same Windows drive letter mapping and if that drive mapping is ever deleted, user cannot connect to db. I use code to modify the link path. https://www.accessforums.net/access/...end-27089.html