ASP vs Access

[Cleis]

Hi all:

Up till now all of my development efforts have been in Access 2.0 through Access 97. I recently got Access 2002 and spent some time reviewing the Data Access Pages. I thought that this was a great addition to a great platform. I then started to think, why not create an entire business solution via ASP attached to a Access 2002 MDB back end?

This is what I would like to do using Interdev.

Create a full feature Application that manages three business core areas:

1. Contract entry, edit, look up, analysis
2. Payment posting per Contract (AR Database)
3. Sales anlaysis and forecasting

At this time, each of the above are seperate Access apps which are in different Access versions (2.0 & 97).

What I would like to do is use APS and merge all of the above into one co-heasive application eliminating the number of front ends on my end users machines and version control issues.

I have what I would consider strong VBA knowledge with a basic understanding of the differences in syntax variences between DAO and ADO. I'm assuming, that like Access 2002, ADO is the default preference in ASP?

I've picked up a Wrox ASP "how to book" and the vb script looks pretty basic. The HTML however, would require a crash course for me. . . but it looks pretty straight forward.

It seems to me that Business Application Solutions are going towards the Web Browser user interface direction? Do you agree? With that being said a couple of questions:

1. Can I create robust reports in ASP like in Access?
2. Are there any issues in using MDB as a back end?
-at this time, I don't have my own dedicated server.
-SQL server at this time is not an option ($)
-There will not be more that 25 users at one time.
3. I'm assuming that if I use Access 2002 as a back-end
I only need one licensed copy on the network?
4. Finally, is ASP the way to go with what I would like to
do?

Any advice or opinions would be greatly appriciated!!!

Rich

 

[jasonsalas]

Hi Rich,

You can do all of that by incorporating your Access DB via the Web. You're limited in the amount of analysis/forecasting upon the data, as scripts largely can only look at a given piece of data and present it if it meets some conditions. Some of the functionality of an Access application can be replicated via ASP for the Web, but it's a lot more intense code.

My friend (an Access DBA) has a LAN app that he wrote and he and I are trying to port it to a Web version with all the same functionality, but we constantly run into snags and have to find a workaround. That's the key...knowing how to translate your business logic to Web format, and then translate this into the proper syntax for ASP.

You're right...ADO is the way to go for coupling an Access DB with ASP.

As for your specific questions:

1) as noted, you can create robust reports...you might have to change the way they work, though. For example, they might have to be event-driven, such as being executed when a script is fired (like pressing a button to generate values).

2) The only condition about running Access as a Web back-end is performance. Theoretically, Access can only facilitate 11-15 users at any one given time (meaning that people accessing resources at that precise nanosecond in time). Errors occur if the DB gets overloaded with requests. SQL Server doesn't have this problem. But, if it's an internal app, you should be able to regulate usage. Also, the amount by which your DB can grow is limited (although I've yet to meet anyone whose table exceeded 65,000,000 records).

3) Right. You only need to access resources from a single DB, on a Web host. I don't believe Access can handle mirroring or rolling over the way SQL Server can.

4) Absolutely!


Also, I recommend the following:

- have all functions predefined and executed by means of stored procedures ("queries" in Access). This compiles and caches the actions needed to carry out a set of instructions, and then results in better performance for every time the SP runs after the first time, being cached.

 

[Cleis]

Thanks so much for your insight! Which type of web server do I use PS IIS?

 

[jasonsalas]

Well, theorretically either MS Web server application would work (IIS or Personal Web Server), but for your needs, IIS would be the better solution (and I wouldn't recommend using Personal Web Server to distribute the type of Web app you're thinking about deploying).