create EXE from database and have several project using the same database.

[quicova]

Hello everyone.

I created a database with forms, querys, etc.
Now I was thinking of creating a exe so everyone can use this database without having access to all the design functions.

the only problem I see about doing this is if we need to use the same database for different project, we need to always create a new exe for each project.

Is there a way to make a empty database exe with just the layout, querys etc but with no data on the tables and have a save, open and save as option.
so we can have several projects using the same database?

I was thinking to create a VB code for the database to delete all data on the tables when the database is open.
and before closing the database exporting all the data to a txt file or something.



them the next time someone opens the database goes to the main form which has a open bottom which imports the txt file into the tables.
this way we can have several txt file for several project and use always the same exe database.

is this the best way to approach this problem?
anyone has any ideas?

thanks so much

[June7]

Maybe you need a split design. Frontend has queries, forms, reports, code, and links to tables in backend. The backend sits on file server and each user runs their own copy of the executable frontend on their workstation.

[quicova]

Hello everyone.

That split design looks like a good idea.
Is there a way to create different backends for different projects and create a buttom to choose which one to open, a button for save as and a buttom for create new project which makes a new empty backend file?

I tried doing a split using the wizard and I get a subscript out of range error, any ideas on this?
Can I do the split manually without the wizard?

Thanks in advance

[quicova]

I figure out how to split the database manually.

Here is the link if anyone has the same problem: http://answers.microsoft.com/en-us/o...b-d17efb9a962c

Now I need to find a way to open the front end database with no tables and create a button to show with backend file to open
and create another button to import an empty backendfile to start a new project

any ideas?

[June7]

Why do you need to create multiple identical structure backends?

Build a master backend db with empty tables and copy it as needed.

However, this will be a maintenance/management headache.