Access ADP

[Stanley]

I have an Access 2000 project using an mde front end and
an mdb backend. I am having repeated corruption problems
and I would like to convert to SQL Server with an ADP
front end. In anyones experience, is this a good approach
as it appears the easiest way to get this done (vs a VB
front end). Any suggestions would be welcomed.
Thanks,
Stan

 

[Sal Rosario]

In my view, this is a good apprach, but if your application uses a lot of
DAO objects in your programming, you will need to do a lot of code fixing to
adjust to ADO which is the supported data access in Access projects.

If you don't need to implement SQL stored procedures, triggers, and so on;
what I would do is migrate the tables over to SQL Server and link to those
tables from within Access without changing any VBA code. In that case, you
are not using an Access project, but you can still take advantage of SQL
Server stability to support multiple connected users.

 

[Larry Linson]

I have an Access 2000 project using an mde front end and
an mdb backend. I am having repeated corruption problems
and I would like to convert to SQL Server with an ADP
front end. In anyones experience, is this a good approach
as it appears the easiest way to get this done (vs a VB
front end). Any suggestions would be welcomed.

Why don't you first visit MVP Tony Toew's site,
http://www.granite.ab.ca/accsmstr.htm and review his section on corruption.
If the tips there can cure your corruption problems, as they have in many
cases, you'll have a whole lot less trauma.

If that isn't satisfactory, save yourself some work by using an MDB with an
ODBC link to the MSDE or SQL Server (or any other ODBC-compliant server
database, for that matter). You will likely have to make some modifications,
but not nearly what you'd have to make if you convert to ADP.

When ADP's were first released, they were promoted (hyped) as the method of
choice in all cases for Access clients to SQL Server; currently,
knowledgeable Microsoft insiders tend to consider the old, tried-and-true
MDB-DAO-ODBC-Server approach to be the method of choice in _most_ cases.

If you feel _compelled_ to convert to an ADP, I'd strongly suggest that you
upgrade to at least Access 2002, as there were significant improvements made
to ADPs in that release. If you are forced, for some reason, to use Access
2000, at least make certain that you have applied all three Service
Releases/Packs (and, too, make certain that you and the management
responsible for the application understand that Access 2000 is no longer in
mainstream support). Access 2003, of course, is the current version and has
all the improvements of Access 2002 in the ADP area.

Larry Linson
Microsoft Access MVP

 

[Lyle Fairfield]

When ADP's were first released, they were promoted (hyped) as the method
of choice in all cases for Access clients to SQL Server; currently,
knowledgeable Microsoft insiders tend to consider the old,
tried-and-true MDB-DAO-ODBC-Server approach to be the method of choice
in _most_ cases.

Last thing I heard is that MS will be doing a test for this.

They're going to develop some specs, then lock Linson, Fenton and a player
to be named later in a room over a month and have them create an "MDB-DAO-
ODBC-MSSQL Server" solution.

At the same time, Fairfield, Wintermeyer and a yet to be selected developer
will prepare an ADP solution under the same conditions.

Better solution wins.

Email Larry or me, or post if you want to apply to fill either open slot.
Outline your background, formal education and reasons for interest.
Applications close July 31. Block September out of your schedule.

 

[Larry Linson]

Last thing I . . .

The referenced post was quite possibly from a troll impersonating Lyle
Fairfield. Lyle is a strong advocate of ADPs, but I can't recall him ever
being so silly in a newsgroup post.