Hi everyone.
I'm about to help a friend out with an Access database (not my primary expertise - especially on distributed apps) that will be used to allow about 25 users to login on form #1 and then input their hours, project type, location and a few other pieces of information into form #2 and then exit. Could be several concurrent users, but ideally they'll only be on for a few minutes a day at various times and time zones, so traffic probably won't be that heavy.
Easy for a desktop application, however these people will be coming into a secured set of folders via the internet -no, i can't talk him into ASP
- and the connection is usually pretty poor.
Normally I would split the app into a backend data db that resides on the server and then install the front end on each PC, but the lousy, inconsistent connection seems like it would be a problem. Open app, dialup, then wait - or worse, keeping recordset connections open while the browser is hung up. This happens as often as not. If I use a disconnected rst, the app may not reconnect and they will have wasted their input.
I probably still split the application in to 1 front and a back end but put them on the server. At least the recordsets will be quick because it will be local, but I'm not sure how many concurrent users it will take before performance becomes a problem this way. No one will be editing the same record, they'll be adding their own data into new records.
Is this a candidate for an ADP project? What is an ADP project??? Any comments, or ideas to look into (related to the thread please...) would be greatly appreciated.
Thanks.
I'm about to help a friend out with an Access database (not my primary expertise - especially on distributed apps) that will be used to allow about 25 users to login on form #1 and then input their hours, project type, location and a few other pieces of information into form #2 and then exit. Could be several concurrent users, but ideally they'll only be on for a few minutes a day at various times and time zones, so traffic probably won't be that heavy.
Easy for a desktop application, however these people will be coming into a secured set of folders via the internet -no, i can't talk him into ASP
- and the connection is usually pretty poor.Normally I would split the app into a backend data db that resides on the server and then install the front end on each PC, but the lousy, inconsistent connection seems like it would be a problem. Open app, dialup, then wait - or worse, keeping recordset connections open while the browser is hung up. This happens as often as not. If I use a disconnected rst, the app may not reconnect and they will have wasted their input.
I probably still split the application in to 1 front and a back end but put them on the server. At least the recordsets will be quick because it will be local, but I'm not sure how many concurrent users it will take before performance becomes a problem this way. No one will be editing the same record, they'll be adding their own data into new records.
Is this a candidate for an ADP project? What is an ADP project??? Any comments, or ideas to look into (related to the thread please...) would be greatly appreciated.
Thanks.
