Split database for several projects

[quicova]

Hello everyone.

I created a database and I manage to split it into front end and backend.
now I'm going to make an EXE of the front end.

My question is when I open the front end, I need the database to be empty, and them create a button that will make the user select which project he wants to open (backend).

I also need to create a button that will create a new empty backend and save it as a new project.

anyone has any ideas on how I can go about this?
thanks so much

 

[Mr. B]

I created a database and I manage to split it into front end and backend.
now I'm going to make an EXE of the front end.

First, I have to first tell you that it is not possible to actually create an exe out of the front-end Access database file. You can create a compiled version and your users can open and use that with the Runtime version of Access.

My question is when I open the front end, I need the database to be empty, and them create a button that will make the user select which project he wants to open (backend).

I also need to create a button that will create a new empty backend and save it as a new project.

Here is a link that should provide you with code that will link your front-end file to a specific back-end file. As for having the database to be empty when opened, you could just have the front-end initially linked to an empty database then when a new database is needed, just make a copy and link to that new empty back-end file.

With that said, I am curious to know if you have really thought this through. Although it is possible to do what you are describing. You are going to have issues if you ever need to report on the data from your multiple databases. If there is any possibility that the data from these multiple project databases will need to be combined to provide reporting over all projects for a period of time then you may want to consider having only one back-end file but have it structured so that each project can be identified and provide users with the ability to enter data for one project at a time, but then when needed you can easily combine the info from multiple projects.

If you have some business rule that dictates that you create these multiple back-end files then so be it, but I just thought I would raise the issue.

Good luck with your project.

 

[quicova]

Thank you for the replay Mr.B

I will have to study the compile version to use in runtime, I'm new to access and create an exe was the only solution I found so that users can't change the code or the design.

The reason for creating several backend files is that each project will be totally independent of each other.

I can't see the link you posted?
can you post it again please. maybe is because I'm a new user and I can't see links.

Thanks so much

 

[Mihail]

I'm sure that this thread on Bytes will help you a lot. Be patient and read the entire thread.

 

[quicova]

hi Mihail,

super complicated thread. I'm very new to scripting to I didn't got anything

and that thread is the reverse of what I'm trying to do. link a specific backend file into the frontend file. and eveytime someone opens the frontend file it is linked to a empty backend file.

 

[Mihail]

and that thread is the reverse of what I'm trying to do

No, it isn't.
From any FE you can switch to more BEs. In the same time the other FEs are linked to the same BE in order that all of them to point to the same BE.

super complicated thread

Is not very simple but not as complicated as you say.

 

[quicova]

thanks for everyone replays.

I was given this link
jstreettech.com (J Street Access Relinker)

sorry I'm not allow to post links yet!!! that sucks

which has a download with exactly what i needed if anyone has the same problem.

you just import it to your database and the code is all done.
it promts the user to which backend file he wants to open.

Thanks so much for all your help.