ADP and Local Tables

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have converted both my front end and back end to using the upsizing wizard.
I read in the "Access 2003 Bible" that in a client/server environment it is
not good to use bound forms because of having constantly open connections.
Is there any way to create and access a local table on the user's hard drive
where the front end .MDP resides and have that front access the table without
having to maintain a connection to the SQL server? Or, maybe this is a moot
point. Perhaps someone can enlighten me. Thanks.
 
ADP does not/cannot have local table. Period.

If yu want the front end have local table(s), you could use *.mdb front end,
instead of *.ADP. Actually, MS's access team recommends *.mdb front end
rather then ADP front end.

Both ADP and MDB front end app are typical two-tier application and
data-bound controls/forms are Access's "advantages" over other developing
tools. It has its suitable scenarios and not suitable ones.
 
Norman said:
ADP does not/cannot have local table. Period.

If yu want the front end have local table(s), you could use *.mdb front end,
instead of *.ADP. Actually, MS's access team recommends *.mdb front end
rather then ADP front end.
Click to expand...

can you point us to where the MS Access team recommends this.
i need to understand why.
tia,
mcnewsxp
 
It was from MS Access Team's blog. I could not remember when I read it, but
it was almost a year ago. I did a quick search, it came up

See link

http://blogs.msdn.com/access/search.aspx?q=ADP&p=1


<quote>
New, More Complete Access Overview
posted Thursday, July 27, 2006 12:00 AM by Erik Rucker
called ADPs or .adp files, provide an alternative to using the Access
database engine by allowing an Access application to connect directly to the
tables in a SQL Server database. ADPs will continue to be supported in
Office Access 2007. To take maximum advantage of the new features in Office
Access 2007, Microsoft recommends the use of linked tables to connect to SQL
Server data. When Access was introduced, installable ISAM drivers were used
primarily for linking to the prevailing desktop Read More

</quote>
 
ADPs are to be replaced with the .NET framework for any advanced database
operations agains a SQL-Server and MS recommends that you use MDB with
linked tables for entry level database operations that doesn't require
advanced features or things like good security, etc. and to use .NET if
linked tables are not sufficient.

It's not that ADPs are bad by themselves but MS doesn't work on this
technology anymore - working instead on .NET - and excerpt for the
integration of the new menu of Office 2007 (yeach!), don't expect any real
change or improvement to ADP 2007.
 
R> I read in the "Access 2003 Bible" that in a client/server environment it
R> is not good to use bound forms because of having constantly open
R> connections.

It's the same as telling car owner that driving it is not good because the
car then is having constantly running engine.

Access is built around bound forms, they are its cornerstone and biggest
advantage. Developing in Access without bound forms does not make much
sense.

Constantly open connections present zero harm both to the server and to the
client. Without the traffic, they don't consume any resources.


Vadim Rapp
 
yes, ADP are a completely superior product in all aspects.

not having local tables is a FEATURE.

you can use persistent tables in the tempDb if you want to..

select *
into tempDb.dbo.tblMyOrders_SPID05
from vwMyOrders

that is faster, more powerful; and less maintenance.
of course; if you bounce the service; you lose everything in the
tempDb.

-Aaron
 
and for the record; keeping a connection open the whole time??

this is one of the best FEATURES in ADP.

you can use @@SPID much like you would use SessionID in the ASP world
to make the key for an ecommerce-type app

-Aaron
ADP Nationalist
 
I was reading these comments regarding ADPs. I've moved several of my
applications from .mdb to .adp format running on SQL Server 2000 and have
seen a significant improvement in speed. One of my applications is also all
based on un-bound forms and still runs great. Vadim said that's pointless. I
would not agree.

What I find disturbing aboutMicrosoft right now is that after pulling me
over to SQL Server 2000 / MSDE and Access ADPs, they now are changing their
direction. For large companies, dropping everything you've worked on and
moving to a new platform, (i.e. VB.NET) is no big deal, but for small
companies that's easier said then done. I have a life outside of work and am
not interested in working at nights to redo what already works great.

What I also find disturbing is that MS is not working on improving ADPs now,
from what i've read here? This seems clear because my Access ADP application
does not allow me to make changes to my SQL Server database via Access
anymore, now that I'm running on SQL 2005. Is there a Service Pack that
resolves this problem?

Also, are their any tools on the market, or from Microsoft that will convert
an existing Access application to VB.net for me?

Thank You
 
Greg;

it is not true; ADP are better supported than MDB going down the road.

VB.net is a friggin PAIN IN THE BUT; it might take you a year or 2 of
fulltime development to be half as fast with VB.net as you are with
Access.

tell your boss to grow up and stop changing directions.

ADP is the best platform anywhere.

All you need to do is right-click SORT to prove it to him.
Right-click FILTER.

-Aaron
ADP Nationalist
 
again; these people that have been spewing lies like this?

they're just fat lazy retards that are too incompetent to learn SQL
Server.

ADP is superior to MDB and VB.net in MANY ways.
Microsoft should have concentrated on 'ease of development' for VB.net;
because as it is; it's friggin impossible.

I've built a LOT with VB.net... don't get me wrong-- I love it for some
things; like ETL for example.

But for data entry and reporting??

ROFL

Access Data Projects rocks.
Don't migrate your db server without researching any potential problems
first.

-Aaron
ADP Nationalist.
 
MS _IS_ working on making ADP able to update server 2005 objects.

I have a friend on the team; he told me that they're working on an
Access 2003 patch for SQL 2005.

-Aaron
ADP Nationalist
 
sorry.

it is DEFINITELY going to be there in Access 2007. I've read it from a
dozen official Microsoft postings.

I'm HOPEFUL it will be here in time for Access 2003. It should be
here; maybe if they did that then I would forgive them for making
Access 2000 and SQL 2000 incompatabile.

I swear; the Access project manager that came up with that decision
should be SHOT.

FAT, LAZY PM-- drive your BMW and abuse developers / end users--
we'll show you, Microsoft!!

-Aaron
 
Back
Top