Access-XP - ADP Should I or shouldn't I???

[Ron_A]

I consider myself an intermediate to budding-expert in developing
using ACC-97. For some time now, on Win-NT, I've been using Split DB's
with backend on server and front end local with all my users. This has
worked great. I'm taking on a new position that has increased my user
base from around 150 to more than 1000. My first project is to build
an employee db that will track vacation time, and serve as a
repository to all future db's that require employee information.
InfoSystems has been pushing SQL Server as the db of choice. I'm
seeing a lot about ADP. Would it be in my best interest to develop
this new project using ADP/SQL Server because of the increase in user
base? I haven't seen any good books on "teach yourself ADP" and would
only have 4-6 weeks to ramp up. I already have Access-XP, but few of
the users do, will I need a runtime module? Will I need a "Developers
Edition" in order to creat XP RunTime code??? Any advise would be
deeply appreciated!

[Larry Linson]

Some very knowledgeable Access developers advise against using ADPs; other
very knowledgeable Access developers advise using them with MS SQL Server
back ends.

My Access client - server database client-server applications have all been
Access - Jet - ODBC - server database and have worked well with user
audiences in the low hundreds.

I think there are a number of factors you are going to have to take into
consideration. One of those is, do you really want a client-server model
with that many users? You may be better served with a web-based application
done with asp or ASP.NET pages and an SQL Server database, or with Cold
Fusion, or some other approach.

Perhaps some who have done larger client-server applications, and who've
done and liked the ADP approach will weigh in with opinions.

Larry Linson
Microsoft Access MVP
"Ron_A" <ro**********@excite.com> wrote in message
news:4c**************************@posting.google.c om...

I consider myself an intermediate to budding-expert in developing
using ACC-97. For some time now, on Win-NT, I've been using Split DB's
with backend on server and front end local with all my users. This has
worked great. I'm taking on a new position that has increased my user
base from around 150 to more than 1000. My first project is to build
an employee db that will track vacation time, and serve as a
repository to all future db's that require employee information.
InfoSystems has been pushing SQL Server as the db of choice. I'm
seeing a lot about ADP. Would it be in my best interest to develop
this new project using ADP/SQL Server because of the increase in user
base? I haven't seen any good books on "teach yourself ADP" and would
only have 4-6 weeks to ramp up. I already have Access-XP, but few of
the users do, will I need a runtime module? Will I need a "Developers
Edition" in order to creat XP RunTime code??? Any advise would be
deeply appreciated!

[David W. Fenton]

ro**********@excite.com (Ron_A) wrote in
<4c**************************@posting.google.com >:

I haven't seen any good books on "teach yourself ADP" and would
only have 4-6 weeks to ramp up. I already have Access-XP, but few
of the users do, will I need a runtime module? Will I need a
"Developers Edition" in order to creat XP RunTime code???

I can't make any recommendations on the ADP front, though for
myself, I've decided that if faced with a SQL Server project where
an ADP would be appropriate, I certainly will avoid it at all
costs.

As to the question of Access XP, its native file format is the same
as Access 2000, so if your users have that installed, you won't
need a runtime installation.

If your users have Access 97 installed, though, you'll need to do
something else. If the users actually utilize A97 for more than
just running your app, then the runtime may not be an option. I
don't know if the A2K runtime breaks installed A97 or not, but it's
the kind of thing I'd worry about.

In any event, you could also still develop in A97 and use ODBC to
connect to SQL Server. It wouldn't be as flashy and up-to-date as
A2K using ADO to SQL Server, but it would probably perform just as
well and would require no upgrades to the existing desktops that
already have A97.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Saintor]

Against all odds, I have yet to see an ADP that performs significantly
faster than DAO with a good back-end engine. But at 1000 users, you need a
web interface IMO.

If you want to go with the developer solution, get an Installer for Windows.
I went with Wise with Sagekey. Sure it was around 1000$ in addition to the
Developer kit, but MS does not seem to be competent for developping custom
package solutions.

"Ron_A" <ro**********@excite.com> wrote in message
news:4c**************************@posting.google.c om...

I consider myself an intermediate to budding-expert in developing
using ACC-97. For some time now, on Win-NT, I've been using Split DB's
with backend on server and front end local with all my users. This has
worked great. I'm taking on a new position that has increased my user
base from around 150 to more than 1000. My first project is to build
an employee db that will track vacation time, and serve as a
repository to all future db's that require employee information.
InfoSystems has been pushing SQL Server as the db of choice. I'm
seeing a lot about ADP. Would it be in my best interest to develop
this new project using ADP/SQL Server because of the increase in user
base? I haven't seen any good books on "teach yourself ADP" and would
only have 4-6 weeks to ramp up. I already have Access-XP, but few of
the users do, will I need a runtime module? Will I need a "Developers
Edition" in order to creat XP RunTime code??? Any advise would be
deeply appreciated!

[JetMaster]

"Ron_A" <ro**********@excite.com> wrote in message
news:4c**************************@posting.google.c om...

I consider myself an intermediate to budding-expert in developing
using ACC-97. For some time now, on Win-NT, I've been using Split DB's
with backend on server and front end local with all my users. This has
worked great. I'm taking on a new position that has increased my user
base from around 150 to more than 1000. My first project is to build
an employee db that will track vacation time, and serve as a
repository to all future db's that require employee information.
InfoSystems has been pushing SQL Server as the db of choice. I'm
seeing a lot about ADP. Would it be in my best interest to develop
this new project using ADP/SQL Server because of the increase in user
base? I haven't seen any good books on "teach yourself ADP" and would
only have 4-6 weeks to ramp up. I already have Access-XP, but few of
the users do, will I need a runtime module? Will I need a "Developers
Edition" in order to creat XP RunTime code??? Any advise would be
deeply appreciated!

Go to: http://www.mvp.com
Best Regards
Joan "JetMaster" Jett, MVP