ASP using an Access database ... lots of problems!
Long I'm afraid ... I'm using an ASP discussion forum (from Web Wiz Guide - I am a complete ASP newbie) with an Access database. A new version of the forum fixes a couple of bugs and is an improvement on the version I am running, so I need to upload it but retain our existing member and post details.
I was told to do this by using the existing database, pasting in the new tables from the new version and inserting a few new columns in some of the existing tables. I could not get this to work properly - the forum took 40+ seconds to load or would not open at all (one person got an error message saying the database was performing too many operations). I checked and re-checked the properties for every field in the database in design view to ensure everything was identical with the new version of the database, but to no avail.
So I gave up and decided to manually re-enter all of the existing data live through the new forum using the new database (I am running this on our site but am the only person accessing it). Fortunately our existing forum hasn't been up long, so is small! This was fine - I registered the members and copied across several threads with no problems by logging in and out as each member. Today I have returned to continue with this (boring!) work and have come up with the following error on the main page, despite it having been fine when it was last opened:
Microsoft OLE DB Provider for ODBC Drivers error '8007000e'
[Microsoft][ODBC Microsoft Access Driver] Not enough space on temporary disk.
/new_forum_new/date_time_functions.inc, line 65 (sometimes it is line 144 instead)
The code triggering the error is pointing to the table in the database where the date and time preferences are stored and it seems to be triggered when this is called by the 'created date' and 'created time' for the fourth forum in the list - the others above it are fine. The preferences have not changed since the last use of the forum and re-updating them makes no difference. I've checked the table in the database and it seems fine to me.
Deleting the forum and those after it which seem to trigger the error causes everything to load properly without errors, but re-adding them manually through the admin section of the forum gets the same error.
I've tried inserting 'On Error Resume Next' at the lines in the .inc page causing the error. This leads to another 'not enough space' error, but in the default.asp and a line which calls up the forum list order details. Having now re-uploaded the .inc with the 'On Error Resume Next' bits removed, I'm now getting the same 800700e error, but stating:
General error Unable to open registry key 'SOFTWARE\ODBC\Brazos volatile counter' (at the same line in the .inc as was triggered before)
To see what it looks like go to ethics forum - new
I am wondering if the whole problem is due to using an Access database, however, at present I'm constrained to doing so and I am fairly certain the forum run by its author is also through Access and it works fine (and is very busy). Very frustrated and confused! Any help would be very much appreciated.
Bug
Peter J. Boettcher posted this at 14:32 — 7th February 2002.
They have: 812 posts
Joined: Feb 2000
Bug,
It's hard to determine what the problem is exactly. While this won't fix your problem you should rename those .inc files to .asp, that is a major security risk. Just out of curiosity, how much disk space do you have.
It sounds like you're using third party software that isn't working correctly.
I don't think the problem is the Access database, but maybe the integration of it into the ASP. Something isn't right. Maybe what you should do is start fresh with the new empty forum and see if it works correctly. If it does then import your data into the new forum database.
PJ | Are we there yet?
pjboettcher.com
Sparklebug posted this at 03:58 — 18th February 2002.
They have: 54 posts
Joined: Oct 2001
Hi Peter. I contacted our site hosts re these issues and asked if the problem might be their end. They came back and said we have 'loads' of disk space and that they thought the problem was probably with the ASP code. However, the problem simply vanished at that point – without me doing a thing. So I suspect it was something their end but perhaps they didn't want to admit it! I've now managed to use the existing database and move it into the new version of the forum by adding some fields – same thing I spent days working on previously took me 10 minutes.
I've since had another error message, which I will put on a separate post as it appears to be a separate issue.
However, I'm intrigued to know what the security issues are re .inc files as opposed to .asp files. Will the files work any differently if they are changed to .asp?
Thanks for your help
Bug
Peter J. Boettcher posted this at 13:28 — 18th February 2002.
They have: 812 posts
Joined: Feb 2000
If you leave those ASP include files named *.inc then all the ASP code will be visable on the client side. So if you hade any confidential server-side info like passwords or database connection strings that would all be exposed. If you rename it to .asp then all that server-code will be executed before it gets passed to the client and nothing will be exposed. I would do this as soon as possible, it's a good habit to get into!
PJ | Are we there yet?
pjboettcher.com
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.