Help with moving Access database (3 Viewers)

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

Code:
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?
 
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.
 
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.

registry.jpg
 
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?
 
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.
 
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?
I had them split and then not split, same results. I will try it again since changing registry.
 
I had them split and then not split, same results. I will try it again since changing registry.
When you used the splitting wizard, what was the file name the wizard assigned to the back-end file and where did the wizard place the file
 
See, this is the issue I am encountering that maybe will not work. I have created the entire database on my PC which has nothing to do with the office that is going to use the DB. So in doing this everything reads my PC. If I don't split anything the entire DB works great on the one computer I am trying it on at their office except for the potential security screen. I am not even trying to put it on another PC yet. If I split I have to do it on my PC because they have no Office program on any of their PCs other than the Runtime I installed. Because of this, after the split, the DB will not work at all because it can't find the split tables.
 
When you used the splitting wizard, what was the file name the wizard assigned to the back-end file and where did the wizard place the file
TimeClock_be and it put it in the folder I am using for the program.
 
See, this is the issue I am encountering that maybe will not work. I have created the entire database on my PC which has nothing to do with the office that is going to use the DB. So in doing this everything reads my PC. If I don't split anything the entire DB works great on the one computer I am trying it on at their office except for the potential security screen. I am not even trying to put it on another PC yet. If I split I have to do it on my PC because they have no Office program on any of their PCs other than the Runtime I installed. Because of this, after the split, the DB will not work at all because it can't find the split tables.
Then you will need a commercial installer so the users can run an .exe file to install it.
 
See, this is the issue I am encountering that maybe will not work. I have created the entire database on my PC which has nothing to do with the office that is going to use the DB. So in doing this everything reads my PC. If I don't split anything the entire DB works great on the one computer I am trying it on at their office except for the potential security screen. I am not even trying to put it on another PC yet. If I split I have to do it on my PC because they have no Office program on any of their PCs other than the Runtime I installed. Because of this, after the split, the DB will not work at all because it can't find the split tables.
Then do you have a routine that allows relinking to a different BE - as an accde the users do not have the ability to change manually, unless it is programmed in to allow them to do it - see Jstreet relinker as an example utility
 
I have mapped a folder on my drive as a hard drive using instructions like this. Then add any required subfolders and place your back-end there to relink. This creates a similar environment.
 

Users who are viewing this thread

  • Back
    Top Bottom