Newbie: asp.net and restricted web server, Access backend?

[Keith R]

I've done some basic programming in VBA and VB.Net 2003 (CF), but have never
had a need to do any web programming before. I have downloaded VB2005
express.

I have a data entry tool that I'd like to re-create to make it web enabled,
moving from and Excel to Access backend. Access is required because I can
put files on the web server, but I don't have tech support or permission to
use any other databases (SQL, etc)- whatever I build has to 'live' within
the same parameters as the rest of the existing web site.

My first question is whether this is even possible with VB.net, or are there
other server settings or controls that must be installed or enabled to
support asp.net- or can I just create my asp pages and stick them in with
the rest of the web site?

Second question, if this is possible- can anyone provide good references on
'best practices' for designing asp pages with an Access back end? I'm
concerned about things like the total number of users/"active" connections
(the total number of records will never be more than 100K).

Thanks for any info, as I start trying to understand asp and whether it can
be used given my system limitations.

Keith

 

[sloan]

You ~can write an appliation with an Access backend. However, I'd suggest
looking at Sql Express as an option.also.

Having said that. If you want to write a backend Access database
application, do so with strict N-layer rules so you don't screw yourself in
the future.


Go here:
http://sholliday.spaces.live.com/blog/

6/5/2006
Custom Objects and Tiered Development II // 2.0



And I would diligently try to get that sample to work with a Northwind.mdb
file.


In the CustomerData class, you will have to alter


private readonly string PROC_CUSTOMERS_GET_ALL =
"dbo.uspCustomersGetAll";
// private readonly string PROC_CUSTOMER_GET_SINGLE_WITH_ORDERS =
"dbo.uspCustomerGetSingleWithOrders";

to something like


private readonly string PROC_CUSTOMERS_GET_ALL = "Select CustomerID
, ContactName , City from Customers;Select OrderID, CustomerID,
OrderDate,ShippedDate,Freight from Orders";
//notice the ; allows 2 select statements.

You also will not be able to use the DAAB 2.0 as the "helper". You will
need to get the EnterpriseLibrary 2.0 version, and work out the
"genericDatabase" connection string to work with Access.


By doing those things, you should see that the backend database shouldn't
matter (that much) when you create a good DataLayer object.
You can use access, but you MUST make good backend datalayer objects, or
you'll have hodge-podged code that will be tied to Access forever and ever.
Even if you think you always will use access, its not a good excuse to
hodge-podge the code. Keep the datalayer CLEAN.


The goal is to use IDataReaders (as your return objects), and not a specific
datareader class.
That way, you can use Access, but you don't screw yourself in the future.

...

PS You will need write permissions on the folder which houses your .mdb
file. I always forget to do this.
ASPNET is the username (normally). And I'd put the .mdb file in its own
folder.


Good luck.

I implore you to try and work thru the sample I provided, instead of just
jumping into it. Making a mistake early will cost you down the road.

 

[Guest]

There are a whole lot of articles on how to write asp.net code to access a
database from asp.net. The permissions can be tricky if you don't have an
idea of how things work. in IIS 5.0 or 6.0 allow anonymous access to your
website. you have to give the account listed for anonymous access
permissions to read and write to your database. The account is usually the
IUSR account by default. IIS will authenticate that account when a request
to your website is made. This is only the very surface of what has to be
setup. The basic points are listed. With just a little research on the
things I mentioned you can get the necessary steps to be running with your
web site.