Data Access Page, what are the other options?

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

Guest

built a database in access hoping to post it to the web interactively. It's
built and works quite well. It took me a while, was a pretty involved and I
have a lot of detail built into it. Now when I come to the part of putting
it on the web using data access pages I'm finding that it is not advisable
due problems with data access pages and that from what I hear they are on the
way out.
What are my options?
The data base is for a pool league. It records scores and figures out the
out come of the matches, puts together team and individual statistics on a
weekly basis. I live in a rural area, collecting the weeks scores and
getting the information back out is a heck of a hassle due to distance
between towns. Having the data base on the web would be great.
 
The best option, from a reliability standpoint, would be a redesign using
ASP.NET with a true relational database as the data store (SQL Server,
Oracle, etc.). However, this is also the most expensive option, so is likely
overkill for your needs.

If you want to use a JET database as the back-end (BE) data store, you
should back up this database using whatever frequency is needed to avoid too
much pain of having to re-enter data since the last backup. This might be
once or twice a day, one a week, or once a month, depending on your
situation. JET databases are very suseptible to corruption when write
operations are interrupted, which can easily happen with a noisy network, or
dropped packets. With that caveat in mind, you can try these tutorials:

http://www.webmonkey.com/webmonkey/backend/databases/tutorials/tutorial3.html

http://www.databasejournal.com/features/msaccess/article.php/3487741

http://www.learnasp.com/freebook/asp/index.aspx


Good Luck!

Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 
Thanks for the responce. I looked at links pretty thoughly to assess the
scope of the project. I can't help at this point to have some questions and
concerns.

First; Yea, to me the concept behind Data Access Pages seems great but
didn't turn out to be functionally useful in the execution, so now Data
Access Pages are dieing off but ,Hey, great idea. So where are things going
from here? Is this concept being droped for Acess? Access 2007 is comming
out does it address this problem? There is I assume a lot of Access data
bases out there and people would love to put them on the web interactivly.
Providing a tool that does this verses having to hammer out all the code
would seem very desirable to a lot of small timers like me.
Second; The links you provided look excellent as, intro/ basic primers but
the some of the information is delevered through the old. I'm sure they
outline the basic process well but I'm looking at learning it and then going
through the process of updating it to the present i.e. some of the writting
is dealing with win 98/NT and we're in the XP going to Vista time frame.
Have things changed much and will things be changing soon that are pretty
radically different that apply to my little project? Heck I'd hope things
are getting simpler. I'm not intimidated by what I've seen but quicker
easier is what I always try to shoot for and building somthing now that will
have to be redone shortly is somthing I'd like to avoid but since I'm new to
this I'm in the dark.

Thank You,
Kurt
 
yeah; MS is a bunch of drunk idiots; they don't understand the web
development market-- AL ALL.

With dreamweaver; you can easily run wizards to create data entry forms
for example; and you can use any language that you would like to use.
it's a nice tool.

DAP are quite powerful; I have seen it in writing that DAP (office web
components) will be supported through the end of 2013; so I'm over
it... use it for the next 7 years.. but for christ sakes; dont use MDB
for anything.. use ADP/SQL, it is a great platform.. even simple
things-- like filtering for the currrent user; you can't do that in
MDB/DAP; but in ADP it's simple

-Aaron
 
domdog said:
Thanks for the responce. I looked at links pretty thoughly to assess the
scope of the project. I can't help at this point to have some questions and
concerns.

First; Yea, to me the concept behind Data Access Pages seems great but
didn't turn out to be functionally useful in the execution, so now Data
Access Pages are dieing off but ,Hey, great idea. So where are things going
from here? Is this concept being droped for Acess? Access 2007 is comming
out does it address this problem? There is I assume a lot of Access data
bases out there and people would love to put them on the web interactivly.
Providing a tool that does this verses having to hammer out all the code
would seem very desirable to a lot of small timers like me.
Second; The links you provided look excellent as, intro/ basic primers but
the some of the information is delevered through the old. I'm sure they
outline the basic process well but I'm looking at learning it and then going
through the process of updating it to the present i.e. some of the writting
is dealing with win 98/NT and we're in the XP going to Vista time frame.
Have things changed much and will things be changing soon that are pretty
radically different that apply to my little project? Heck I'd hope things
are getting simpler. I'm not intimidated by what I've seen but quicker
easier is what I always try to shoot for and building somthing now that will
have to be redone shortly is somthing I'd like to avoid but since I'm new to
this I'm in the dark.

Thank You,
Kurt

I agree with Tom that ASP.NET is a great way to go. Things have not
changed radically from Win98 through WinXP but they will soon. If you
can wait for Vista, I think the Windows Communication Foundation (WCF)
will provide some interesting new possibilities enabled by XML
underpinnings. In any case, see what WCF offers to help solve this
problem when Vista is released. As a slightly related example, it's
going to be possible to update data automatically from emails. I don't
know if this idea will fare any better than DAP's.

James A. Fortune
(e-mail address removed)

The only difference between the installation software for Windows NT
2003 and Windows NT Server 2003 is some registry settings. -- Ed Steele
 
Win98?

did people actually use that?

I started using NT workstation the first day I saw it since 9x was too
crappy / crashy for me

-Aaron
 
Hi James,
As a slightly related example, it's
going to be possible to update data automatically from emails. I don't
know if this idea will fare any better than DAP's.

I saw a recent demonstration of this new capability, at a recent meeting of
the Pacific NW Access Developer's Group (PNWADG). My first impression is that
it is a pretty cool technology. The only part that seemed a bit strange to me
is that the subject line includes a long GUID string, when one receives the
reply back. My thought is that Microsoft could have, and probably should
have, hidden that GUID from view.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 
I just finished up a Microsoft Visual Web Developer 2005 express edition
video tutorial. I see a little bit now of what your saying about ASP.NET.
The whole thing looks pretty interesting. Thanks for directing me that way.
Kurt
 
I just downloaded SQL Server Express, I'm wondering if I can transfer my
Access Data base over to it?
 
Due to the small scale of my project the investment of spending a lot of
time writing code is not going to be off set by it performing a large volume
of work for a large group of people. The advantage this has is that many of
my solutions do not have to scale up to a large level or address some
security issues. Rebuilding my database as an Web based application is a
task I would like to avoid at this point after researching it. I have the
application on my computer I just need a Web based data entry and collection
tool. What I think may be a useful factor in finding a solution is that I
have no need for instantaneous updating and posting to and from my database.
In fact my queries and reports are best run once all one weeks data is
collected and reports are not needed until the beginning of the matches the
following week. Once I run the reports I can just post them to the web on
static pages. Given the situation I don’t need a supper dynamic Web page.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top