Converting To ADP, Reference Recommendations

[boborta]

I have been creating Access applications since version 2.0 and may soon
become involved with a project that will convert an existing database
into an ADP. I would consider myself verbose in VBA, but inexperienced
using a SQL server back end. Typically when faced with a new challenge
like this one, I will read technical articles & books plus start
experimenting with code. I am sure there are many of you out there
that understand the issues I will have to confront (it worked in
'just' Access, but now....). I would appreciate recommendations
regarding books, web page links, etc., that will be helpful in my next
project.

Access version 2000 - possibly moving to 2003 next year.

Regards,
Bob

 

[dbahooker]

I wouldn't use Access 2000; but it's possible.

Microsoft made Access 2000 and SQL 2000 incompatible.. the retard that
made that decision in redmond should be sitting in an unemployment line

It really depends on what you're trying to do
basically; in a nutshell-- dont use any user defined functions; on the
database side-- for SQL 2000.

and if you're writing sprocs and views; I would definitley use
something other than 2000; since 2000 doesn't support design view for
sprocs; if i remember correctly

I would reccomend taking a look at 'Client Server Apps with Microsoft
Access' and 'Professional SQL Server 2000 Programming with MIcrosoft
Access'

 

[Sylvain L.]

There are many limitations and bugs that have been removed from ADP 2000 to
2003, so it will be a good idea to switch to A2003 as soon as possible.

For the rest, ADP is not really supported anymore by MS, so you will have
difficulties finding technical articles, books and patches (if you find a
bug, it will be a total loss of time for you to raise a technical incident
at MS on this). The current trend is to go with MDB, linked tables and
passthrough queries if your need are light (no real security, no big
procedures to be used as the source of bound forms, etc.) or to go to the
..NET Framework otherwise.

The newsgroup about ADP is microsoft.public.access.adp.sqlserver and
probably that you will find some good information there if you take the time
of reading the previous posts. (Go on google is necessary:
http://groups.google.ca/group/microsoft.public.access.adp.sqlserver ) and to
my knowledge, I don't remember any other good source of online information.

The only book to have been ever published about ADP is "Microsoft Access
Projects with Microsoft SQL Server" by Ralf Albrecht and Natasha Nicol.
However, I'm not sure if you will find any more information in this book
than by reading older posts on Google. (Much of this book is about some
coverage on ADO and SQL-Server. This is a good starting point if you don't
know anything about ADO and SQL-Server; however, if you take into account
the high price of buying this book today, it's probably a better idea to buy
instead some other books directly related to these two subjects and
particularly to SQL-Server.)

The only other thing that I would suggest would be that whatever the final
solution you choose, starting right now studying about SQL-Server won't be a
bad thing. (And even if finally you don't get involved in this ADP project;
this would still be a very good idea.)

 

[aaron.kempf]

Sylvain

you are a lying fucking asshole.

Stop spreading misinformation you stupid ****


MDB is the one that is going away.

There have been THREE BOOKS that specialize in Access Data Projects.

Maybe you should lose the training wheels Sylvain; and stop spreading
misinformation before you find a brick thrown through your window

 

[boborta]

Thanks to all for the replies.

My employer is trying to move to A2003, but this version has a DITSCAP
security problem (what it is I don't know). Until IT and the
government are satisfied with 2003, we are stuck with 2K. This is the
heartbreak of working in a 'locked down' environment. This means
dd-ins are not possible, which is a shame.

Again, thanks for the replies.

Regards,
Bob

 

[aaron.kempf]

well... ADP should work great.

make sure that you have the latest service pack of Office 2000 if
you're going to touch SQL 2000.. those bright young lads; over in
Redmond-- think that it's acceptable to ship Access 2000 and SQL 2000
with known incompatabilities.

ROFL

so included in one of the service packs is this add-in that improved
SQL 2000 - Access 2000 ADP interactivity.

I just would still avoid UDFs like the plague in Access 2000 ADP

I built crazy complex ADP on Access 2000.. I mean; dozens and dozens of
them.
yes; it is a little bit quirky compared to 2002/2003; but it still
works great.

AND NO, IT IS NOT GOING AWAY.
Mdb is the format that is going away

 

[dbahooker]

I think that you should convince your superiors to fly some B52's over
Redmond and say 'fix Access or else'

you got my vote!!


-Aaron

 

[aaron.kempf]

Mine also

Shit; I'd settle for sending in some disgruntled Iraqis

-Aaron