Learning Data Access Pages

[Ray S.]

I'm trying to learn how to create, connect, and use data access pages. I'm
working from a copy of the Northwind database sample. When I copied the
database objects, the data access pages would not copy over. What do I need
to do to make the data access pages work?

 

[Dale Fye]

If you are working in Access 2007, you are out of luck. Microsoft dropped
the DAP from the 2007 version of Access.

 

[Sylvain Lafontaine]

The Data Access Pages are ordinary HTML pages, so you usually put them on a
web server but you could also store them on your local hard drive and open
them in Internet Explorer.

However, unless you have a very, very good reason to learn them (for
example, you have been asked to modify a legacy DAP page), it's a total loss
of time than to learn them. Also, they have been deprecated in Access 2007.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

 

[Mark Andrews]

Go down the asp or asp.net route instead. Or possibly php.
If what you want to do is real simple there should be tons of little
examples of using simple asp pages
to enter or view data from an Access database. ASp.net is a bit more
difficult to jump into but would be the current way to develop web apps.

Also in general probably better to use a database other than Access for web
applications.

My two cents,
Access consultant recommending not to use Access (very rare),
Mark
RPT Software
http://www.rptsoftware.com

 

[Armen Stein]

Go down the asp or asp.net route instead. Or possibly php.
If what you want to do is real simple there should be tons of little
examples of using simple asp pages
to enter or view data from an Access database. ASp.net is a bit more
difficult to jump into but would be the current way to develop web apps.

Also in general probably better to use a database other than Access for web
applications.

My two cents,
Access consultant recommending not to use Access (very rare),
Mark
RPT Software
http://www.rptsoftware.com

Hi Mark,

We're Access consultants too, and I'm an Access MVP, but you need to
use the right tool for the job. We don't build web applications that
use an Access back-end. We use SQL Server. If you're going to spend
the money on ASP.NET development, then you can spend the money on SQL
Server (possibly zero if Express will meet the requirements).

I'm not saying that Access doesn't work as a web back-end; it
certainly can. I'm just saying that it isn't really built for it, and
if a customer is paying us to build a robust web application, we need
to use the right components.

So there's at least two of us, and we're up to four cents.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

 

[Ray S.]

I'm working on developing a database application to manage lists of
suppliers, products, customers, and order processing. It would be nice to
have web access. I've been using MS Access (2003) for a few years now and
have gotten great help from this group. So, are you suggesting that I look at
another database program to use with ASP.Net and SQL Server?

 

[Armen Stein]

I'm working on developing a database application to manage lists of
suppliers, products, customers, and order processing. It would be nice to
have web access. I've been using MS Access (2003) for a few years now and
have gotten great help from this group. So, are you suggesting that I look at
another database program to use with ASP.Net and SQL Server?

Hi Ray,

Our preference in this scenario is often a hybrid approach:

SQL Server back-end database, with views, sprocs and functions that
handle much of the business logic and calculations.

Access front-end desktop application for a few "power" and "admin"
users, using client-server techniques such as those outlined in my
PowerPoint presentation Best of Both Worlds (at
www.JStreetTech.com/Downloads). We do not use Access to store data in
this scenario, it's just for the front-end application.

ASP.NET front-end web application for external and all other users.

The ratio of functionality between Access and ASP.net can vary widely,
from mostly Access and just a "light" web front-end, to mostly ASP.NET
with just a small Access application for occasional system admin and
maintenance.

Sometimes we add SQL Server Reporting Services for more powerful web
reporting. These can be called from the ASP.NET site or the Access
front-end.

Hope this helps,

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

 

[Ray S.]

OK, I've done some work with SQL Server as back end with Access 2003 front
end, but don't have a lot of experience using ASP.NET...can you suggest a
site or book to get me started learning how to use it?

 

[Armen Stein]

OK, I've done some work with SQL Server as back end with Access 2003 front
end, but don't have a lot of experience using ASP.NET...can you suggest a
site or book to get me started learning how to use it?

Hi Ray,

ASP.NET is a huge topic - it's a whole web development platform. I'm
not an expert on it - there are developers on my team that know a lot
more than I do (thank goodness There are many books on the
subject - I would focus on those that include an emphasis on database
operations, not just the programming. You can also check out web
sites like www.4guysfromrolla.com and
http://msdn.microsoft.com/en-us/asp.net/default.aspx.

If you have a critical project to accomplish, you might want to enlist
the help of a consultant to work with you - I'm not sure you would
want it to be your very first project. A good consultant will not
only guide you and do most of the work, but will also not mind if your
goal is to learn from them and eventually take over the support and
enhancements yourself.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com