Create Tables on load

[tristandoo]

Is it possible to create tables and have them be saved in the users local files?

The way I am looking at this is:

Front End DB is stored on a server accessed by everyone
user opens front end and the tables will be created automatically for that specific user since every users data will be different
user enters data and saves it
user prints off report



(attached is the DB if you want to take a look)CNC Order of Operations.zip

[June7]

Better to create temp tables in the frontend as part of the design and leave them permanently then code deletes records. They are called temp because the data is temporary, not the table.

Why do you need temp table? Why not just a query as report RecordSource?

[tristandoo]

Never have heard of having temp tables. Would it be better to force the users to save as and save it inside their own documents?

[Bob Fitz]

Front End DB is stored on a server accessed by everyone

I'm not sure if that would work. Usually with split DBs, you have a shared Back End and each user has their own copy of the front end.

[June7]

I did not catch that statement before.

As Bob said, each user should be running their own copy of the frontend.

[tristandoo]

So again would it be easiest for the students to have to save as (non split) so they each have their own copy?

[June7]

If there will be multiple simultaneous users, the db should be split. All data into one shared backed. Code manages what records each user views. This means a login procedure is needed. If you have to manage design of this database and distribute it, it should be split. Because you can't do edits and give out a new database with each user's data. They would have to import their data from the old version to the new version. That's a burden to the users.