Front end with 50 different forms

[kennethrl]

I have a database with 50 different entry forms. The front and back end are split. Currently there are 50 tablets each one is loaded with the 50 forms. One form is used by one person (the same form is not used by two persons at the same time). The backend is a SQL server.

I would like to have the Front end, containing the forms, to be placed on a server and have the tablets access the forms from the server.

Would that be possible?

I tried a mini trial with two tablets using server containing the forms and it worked successfully. I am wondering what would happen when 50 tablets are using the Front end server.

 

[llkhoutx]

It's bad practice having all users simultaneously using a front end. Use user should have his/her own front end or a batch file downloading a front end from a share drive when necessary.

 

[kennethrl]

Thanks for the reply.

What I was hoping to do is have the ability to update the forms when needed without having to update all the tablets. A centralized location would have been good.

A batch file would take to long to download, unless you could download only the form you need. Is that possible? How would I do that within ACCESS?

 

[llkhoutx]

Individual forms can't be downloaded. An Access program is a single unit.

A method I've used before is to have a front end on each user's PC, which when started up compares it's versions number with a version number on a shared drive. If the version numbers are different, user (at his/her) discretion is advised to download the new version. The new version may not be needed.

It should take very little time to download a new front end, regardless. 2G (maximum size for an Access file) files are copied and replaced very quickly.

 

[Galaxiom]

Fifty different tables with fifty different forms for fifty different users seems an unlikely way to construct a database. I'm guessing you have fifty nearly identical tables and fifty nearly identical forms. Why have you done it this way? You probably only need one form configured for the user.

 

[llkhoutx]

I disagree with Galaxiom. Your database could easily have an enterprise data warehouse back end his by a very large number of users.

 

[kennethrl]

Your comments are appreciated.

The current setup of the database does have the all the forms on the individual tablets.

Updating the individual forms is the problem. The tablet users ( which inputs the data) are not computer literate and would have a problem uploading the revised forms. Is there a way to automate the updating of the forms only when it is needed?

 

[namliam]

why have 50 forms for 50 users?

Why not have a single DB with a single Form.... Sounds like you are using the forms to differentiate between the different users.... where perhaps you can "simply" use the username or "desktop" name to differentiate the users.

 

[kennethrl]

Each form represents a different part being tested, each form is unique to that part.

 

[Galaxiom]

OK it is a coincidence that there are both 50 forms and 50 users but I hope you realise why both namliam and I questioned it.

I will still tell you that your database is fundamentally flawed. You are storing information in the structure so every time you need to add a new part or a new test you must alter that structure and redistribute new forms. Hence the situation raised the question.

An appropriate design allows new parts and tests to be added by adding records to tables rather than reconstructing the tables.

The single table required to hold the test results should have a field for PartID, TestID and Result. PartID and TestID are the keys form tables that hold the general information about the parts and tests.

BTW. It is amusing that the only post you thanked is the one by Ilkhoutx that suggested why you might have so many forms especially when the reason they gave is nothing to do with your situation. Thanking those who help you maintain your illusions is not the way to better understanding database design.

 

[namliam]

having a form for each part is a strong sign that there is a flaw in your design

99.99% of all cases parts and tests should be records, not forms...

(i.e. Agreeing strongly with Galaxiom here)