Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unstable Access back-end

Status
Not open for further replies.

Stegmite

Programmer
Aug 18, 2004
36
US
I have a simple "online store" set up using Visual Studio as a front end and Access(2k) as a back end. I have 3 pages, one to display the items in a datagrid, one to verify the item and enter a quantity desired, and third is a "shopping cart". The users don't actually pay for it on this site, it's more or less a tool.
The problem comes when I put the project on our server. When the user selects an item from the inventory page, it is supposed to send all the information via sessions to the next page, and so on and so forth. When I built the project on my machine, it worked without so much as an error. However, once it was put on the server (WIN2003, IIS4) it will only work correctly some of the time. Most of the time the problem appears that the sessions aren't passing the data.
Does anyone know how I can correct this problem?
 
Access is exactly what your title says, unstable, in a web environment. I highly recommend using SQL2000, Oracle or MySQL. Your local machine works because everything is on same box.

But Access has nothing to do with session variables passing. Are you sure this is the problem? Try taking the connection to access off and passing variables from page to page. Let us know how it goes.
 
May not be the cause of the problem but are you sure it is IIS4 on W2003? I thought W2003 had IIS6? If you are correct it may be worth upgrading as IIS4 is fairly old and there were some issues with it.

----------------------------------------------------------------------

Need help finding an answer?

Try the search facility ( or read FAQ222-2244 on how to get better results.
 
IIS6 is definitely the "default" IIS version for 2k3. I could not imagine someone wanting to use IIS4 now in general let alone on W2k3. Typo maybe? If you are somehow using IIS4 on 2k3, which I'm not even sure is possible you should really stop...

All hail the INTERWEB!
 
Veep,
Won't say in this particular instance that access was to blame, but generally speaking...

access just isn't a desirable backend for any remotely serius webapp...maybe i'm just a bit spoiled with oracle, though.

All hail the INTERWEB!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top