Data Access Pages

[Guest]

I am researching Data Access Pages for a project at work. I've seen a couple
people's comments that DAP's did not work well for them and they do not like
them. Has anyone used them and would recommend them?

I would also appreciate any help on where I can find more
information/discussion, on how DAP's work and are used. Perhaps even
examples.

My company has an Intranet. My department is considering our options for
creating a "contact management" database to put it in simplest, and it would
be nice if part of it could be accessed through the Intranet for research and
data entry. People would also access the database itself through our network
when they're connected. The database will be pretty robust and probably have
table links to other sources. In addition, more than one person will be in
it at a time, up to around 20 is possible at this point. It would be great
if I could create web pages/forms that can be accessed from anywhere.

Any thoughts?

Also, what does "deprecating" mean? I can't find it at Dictionary.com!
I read a posting that Access is "deprecating" DAP's; what does that mean?

 

[Guest]

I can help you with the meaning of deprecating. Its common usage now means
"to bellittle or mildly disparage". Its older meaning was "to express
disapproval of". Sorry I can't help with your main question.

 

[dbahooker]

go ahead and try 'data access pages' but make sure that you're using
'Access Data Projects'

I have seen it in writing from Micorosft that they will support office
web components until 2013 at least.

-Aaron

 

[Ken Snell \(MVP\)]

See microsoft.public.access.dataaccess.pages newsgroup for some more info
about DAPs.

Deprecating means that Microsoft will not support the building / editing of
DAPs as a regular feature in 2007 ACCESS in acmdb file format, but 2007
ACCESS will still run DAPs for earlier versions.

DAPs are significantly different from regular ACCESS -- they must use
VBScript, not VBA; they use ADO recordsets, not DAO; they are limited as to
when queries are updatable or not (often not updatable even if the same
query is updatable in regular form); they have very little debugging
capability and almost no error messages when script is wrong and no compiler
errors provided; they have numerous ideosnycracies that are not well
documented; you cannot do DLookup or other types of features for displaying
related data on a DAP; cannot produce reports; etc.

I've done some work with them for a special application, but I do not prefer
using them at all. Too many hours needed to figure out what I already know
is easy to do in regular ACCESS, and then the limits are frustrating.

 

[dbahooker]

correction

who the **** uses DAO anymore

if you use Access Data Projects; you can devlier a very-high
performance Data Access Page in maybe a day. It is a much much better
longterm solution than MDB.

And I disagree with Microsoft's policy of not having a replacement for
this technology before declaring it obsolete.

they can't remove functionality until a replacement is found

and Sharepoint? That _SURE_ isn't a replacement.