Help with moving Access database

[Technics]

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.

 

[LarryE]

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

 

[Technics]

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.

 

[Technics]

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.

 

[LarryE]

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.

 

[GaP42]

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 you can incorporate as a module in yours to allow users to do this. There are other examples.

 

[DHookom]

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.

 

[arnelgp]

select and download the version of Access you have in this site:

Ribbons for Access 2007 / Access 2010 – Trusted Locations

Access 2007 Ribbon Website * Access 2010 Ribbon Website * Home of Ribbon Creator

www.accessribbon.de

and it will put your apps in Trusted Location without manually messing
with the windows registry.

 

[sonic8]

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

NO. The Access Runtime is a different edition of Access than the full edition.
If you install the full edition but do not license it, it will be degraded to "read-only" operation, which has similar limitations as the runtime edition, but is still very different in detail.

 

[gemma-the-husky]

NO. The Access Runtime is a different edition of Access than the full edition.
If you install the full edition but do not license it, it will be degraded to "read-only" operation, which has similar limitations as the runtime edition, but is still very different in detail.

I always thought it was the same. It must be easier for MS to just produce one version and limit what it can do than maintain 2 different versions. I'll take your word for it though.

 

[Technics]

This was 2011 so you're correct, I may have had a similar idea.


please post a picture of the registry keys you added so we can see that they are added correctly and into the correct hive.

 

[DHookom]

The path is a folder, not a file.

 

[Technics]

I would like to thank everyone for your input and help with this project. With your help I finally got it right. I realized that it was just not going to work with only Runtime on the PCs so I installed full blown Office on one of the PCs. Once I did that I got all the split tables to line up and good location for the database. At first on the other PC with Runtime I was still getting the potential security risk but I just deleted anything to do with locations and started from scratch. I ended up with the location setup below and it worked for everything. Again, I really appreciate everyone's help.

"Path"="\\\\SERVER-PC\\Time Clock\\"
"AllowSubfolders"=dword:00000001
"Description"="Time Clock Location"
"Date"="08/25/2025 18:54"