A long time ago Larry Linson (MVP contributor to this group) made a point to
me that mdb's could do anything ADP's (Access Projects) could by using
linked tables to leverage Sql server databases. It's been years since then,
and I still sometimes think about that statement when evaluating the
usefulness of the ADP's I build. Larry and I discussed this technique and
he found it "Credible" (hope you don't mind me quoting you sir) so what the
hell... here it goes - this is for all you die-hard ADP guys (and gals of
course). I know there have been long, drawn out debates over the very
subject at hand, some I have read and been a participant... and perhaps this
recommendation of usage has even came to surface - however, I felt it had
not been mentioned before by the way Larry responded.
After working with ADP's since the birth of A2K, I have found many
advantages that suit me... but what about you? Please understand, this
thread is not an open invitation to bash ADP's (let's try something new),
but rather a constructive way to figure out what tricks people are using
that make them "valuable" - ok? So, without further delay... here is one
innovative trick out of my bag in which I have kept for myself for some
time... yours for free if it's new to you...
Note that ADP's connect to Sql Server using an OLEDB connection. This type
of connection can and will definitely span further than the local network,
in fact it can span to any IP Address that has port 1433 (Sql Server) open
and Sql Server/MSDE running. Perhaps the strongest advantage ADP's have in
my business is that I can deploy them to multiple locations while hosting
the database. For a monthly fee, customers get a managed database and do
not incur the expense of a server. This model simply fits the small branch
office scenario "like a glove". Then, using bound forms and intelligent
Stored Procedure design, I have a very tight, fast performing (by keeping
records down), rich, and believe it or not... a secure delivered ADE
application.
How many people have a website that uses a Sql Server database? If so, did
you know you can more than likely connect to it with Access as a Project and
do whatever you want with the database... as long as you have the
credentials? Most, if not all ISP's who host Sql Databases allow you to
connect with Enterprise Manager - you can use those same credentials to
connect your copy of Access. Work with Data, build new queries, build some
forms for maintaining data, deploy them as an alternative to building
complex, yet featureless web page based maintenance systems.
I believe this is new with AccessXP, but did you know that you can now link
many flavors of tables to ADP's? Yes, Paradox, dBase, MDB's, and any ODBC
or OLEDB accessible engine... to name a few. Look into it if you have a
need for this. You could always link some of these from Sql Server, but now
it's a right click and link option in table view.
Anyway - I hope this thread stays positive and uncovers some really good
features that ADP's provide to working developers.
Professional replies are appreciated.
--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access
