Help with moving Access database

[Technics]

I designed a database on my computer, with help from this great forum, but I need to put it on a totally different system/location. The database will be on a server and it will be accessed from two workstations all using Access Runtime. There is no Office programs on any of the PCs. I have changed all the info in trusted locations and it works but every time I open the database I get the potential security risk and have to click open. It opens and works but I don't want them to get the screen and have to it open each time. I have location as \\SERVER-PC\Time Clock\TimeClock.accde and as I said this works other than potential risk screen.

 

[DHookom]

Each user should have Access untimely installed and their own copy of the front-end file. The f-e must be in a trusted location.

 

[gemma-the-husky]

I don't think you can avoid that message with an unlicensed copy of access. You have to set the location/database as trusted somehow. You only have to click "yes" once on opening don't you?

 

[LarryE]

You can create trusted locations on their PC's by adding the correct registry keys. I can't do the research right now but someone else may be able to post them.

NO ONE needs Office except the developer unless the app automates one of the other products. The users should be fine with the Runtime engine.

You can open an .accde file without full ACCESS? I didn't know that.

 

[GPGeorge]

You can open an .accde file without full ACCESS? I didn't know that.

A potential problem in that scenario would be unhandled errors crashing the database. So, it needs to be rock-solid, but otherwise it's a good plan.

 

[gemma-the-husky]

You can open an .accde file without full ACCESS? I didn't know that.

Ah, but runtime access IS full access,just not licenced. You can't run an accident without installing Access of some sort.

 

[LarryE]

That's what the Runtime is for You can't get to design view on any object.

I knew that. I just always thought it needed to changed to a .accdr file. Good to know.

 

[RonPaii]

I do that for neatness and also just in case the user has a full version of Access installed. If you open the .accde with full Access, you get to the Nav pain and you can change, tables, queries, and macros. The only things you cannot change are forms, reports, and modules. So the extra step of renaming to .accdr prevents access to the Nav pain.

I have a ACCDB FE using runtime on about 35 workstations with out problem. All function have error trapping an logging. If you install the FE on the same path on all computers, you can export the section of your registry with that safe path then merge on each workstation, (requires admin rights on the workstation).

 

[Technics]

I know that if even one computer had full blown Office I could put the database on the PC and it would create the correct path since all the PCs are connected through a domain but there should be a work around for just using Runtime. Everything works in the program as should. I just get that opening security risk.

 

[RonPaii]

I know that if even one computer had full blown Office I could put the database on the PC and it would create the correct path since all the PCs are connected through a domain but there should be a work around for just using Runtime. Everything works in the program as should. I just get that opening security risk.

If you know your FE will be placed in a constant path such as C:\YourCompanyName, you can then add the same path to your computer, configure that path as safe location. Now open regedit, go to that location in your registry and export the key. Distribute that file with your FE, then on the user's computer, right-click on the file and select merge (requires admin rights). This will add that path as as safe location and your FE will not pop-up the warning.

 

[isladogs]

Pat
There has never been a version 17.0 for Office
Every version from 2016 onwards including 365 is 16.0

 

[Technics]

I knew about the registry edit so I already created Path: \\SERVER-PC\Time Clock\TimeClock.accde which is the exact path for the database. I did not add anymore than the path. Is the triple and double backward slashes needed throughout the path as you have in one of the examples.

 

[Technics]

I added AllowSubfolders and Description but doesn't seem to help. Also Network Locations.

 

[RonPaii]

I added AllowSubfolders and Description but doesn't seem to help. Also Network Locations.

The reg file I am merging has been in use since 2016, before moving to 365 and 64 bit.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Access\Security\Trusted Locations\Location0]
"Path"="C:\\YourPath\\"
"AllowSubfolders"=dword:00000001
"Description"=""
"Date"="3/24/16 3:34 PM"

 

[isladogs]

Don't know where that number came from Colin. I didn't review the file in detail. It was dated 2011 and so has been around for a while --- I did mention SPECIFICALLY that the OP would need to change the Access version to whatever he was using.
Thanks for the heads up though.

Back in 2016 or so, I decided to ‘future proof’ my application installations by adding 17.0 to the registry trusted location scripts that I circulated with my commercial and some free apps.
I know some of my clients have 17.0 listed in the registry as a result. It does no harm but neither does it do anything.
So possibly you have 17.0 for the same reason

 

[Technics]

The reg file I am merging has been in use since 2016, before moving to 365 and 64 bit.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Access\Security\Trusted Locations\Location0]
"Path"="C:\\YourPath\\"
"AllowSubfolders"=dword:00000001
"Description"=""
"Date"="3/24/16 3:34 PM"

I have tried all of this with no progress. My database is on D drive of server 2019 and I have tried no mapped drive as most things I find say don't use mapped drives. Server is \\SERVER-PC. I tried using it mapped anyhow T:\TimeClock.accde but did not work. Is your database on the same PC where you're using the program? I can't do that because it is going to be used by several so all changes have to go back to same database. The above does not really portray a real registry key. Can you maybe do a screen shot of that part of your registry?

 

[RonPaii]

I have tried all of this with no progress. My database is on D drive of server 2019 and I have tried no mapped drive as most things I find say don't use mapped drives. Server is \\SERVER-PC. I tried using it mapped anyhow T:\TimeClock.accde but did not work. Is your database on the same PC where you're using the program? I can't do that because it is going to be used by several so all changes have to go back to same database. The above does not really portray a real registry key. Can you maybe do a screen shot of that part of your registry?

You don't need to worry about safe locations for the BE database on the server, only the FE on the workstations. The security prompt is about running code and macros not access data on the server.

 

[Technics]

I am doing all the registry edits on the FE workstation using an .accde file on the FE. I have no problems actually accessing the database on the server.

 

[LarryE]

I don't think you even split the file into front-end and back-end files, so you can't distribute the .accde to multiple users anyway. Did you split the original .accdb file?

 

[RonPaii]

I am doing all the registry edits on the FE workstation using an .accde file on the FE. I have no problems actually accessing the database on the server.

View attachment 121237

On your computer using Access, add the folder to your safe locations.
Use RegEdit to locate the registry key. In my case [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Access\Security\Trusted Locations\Location0]
Export that key to a reg file.
If you open it in Notepad, it should look similar to the one I posted.
Copy the file to a 2nd computer, right click and select Merge.
That same key should be on the 2nd computer. The FE should now open without warning.