Access unstable?

Access unstable? (Full Version)

All Forums >> [Web Development] >> ASP and Database

Message

sarge -> Access unstable? (3/4/2001 20:13:00)
Hi- I'm developing a site that's driven by an Access database, and I've had a recurring problem:- >[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x3d0 Thread 0x744 DBC 0x= 17b23fe4 Jet' When it happens, I contact my host and he reloads some server software, and everything is OK for a while... The host now tells me that Access is known to be 'unstable', and that I should switch to SQL. Can anybody offer some 'words of wisedom' ?? Thanks, Brian

Elecia -> RE: Access unstable? (3/4/2001 20:23:00)
How large is the database?

sarge -> RE: Access unstable? (3/4/2001 20:46:00)
2MB at the moment, and it will grow to about 3MB.

Elecia -> RE: Access unstable? (3/4/2001 21:19:00)
Well Access is not intended to handle really large amounts of data. At the last Vbits conference the Microsoft Guru's were not advocating using Access if your tables would be approaching the 80,000 record range. Because Access is unstable at that point and the databases do have the potential to corrupt making your data irretrievable. It would also depend on the version of Access that you are using 2000 is a little more robust than earlier versions. Access offers a world of versitility and because of that it is not nearly as robust as SQL. SQL is a major investment however and unless you have the money to spend you might want to consider other options. Say splitting your data out into more than one database for storage and then create a single database to link all of the tables to. This gives you one database that you have to interface with but multiple storage databases. Also I've had Access databases that were big enough to choke a horse and never had any trouble (knock on wood) I don't know who your provider is but they may be your problem. Maybe this will be some help to you. EE

sarge -> RE: Access unstable? (3/4/2001 22:10:00)
Thank you very much for your advice Elecia. The d/b has under 5000 records, so perhaps my host (atfreeweb.com) could be suspect...?? I'll give some thought to splitting the d/b, and I'll upgrade from 97 to 2000. (This sounds a cheaper alternative to buying SQL, if it works). Thanks again, Brian

Spooky -> RE: Access unstable? (3/5/2001 20:17:00)
Possibly try changing to an OLE DB connection if you are not using one currently? I did have the full explanation at one stage but couldnt find it again....

FPGuy -> RE: Access unstable? (3/5/2001 18:41:00)
I was getting what looks like the same unable to open registry key error in a much smaller database and a compact and repair fixed it.

sarge -> RE: Access unstable? (3/7/2001 20:20:00)
FPGuy- Thanks for your input. I've solved this particular error in the past (early days) by fumbling my way through re-doing everything, including compacting etc. It's now come down to a definable 'inconsistency' by the host, and its a real pain! Thanks anyway. Spooky- I'm feeling humbled, and very very ignorant. I had to look up 'OLE'... and all I managed was a translation. I appreciate that you are not in the business of enlightening idiots, but could you please point me in a direction.. Thanks, Brian

Spooky -> RE: Access unstable? (3/7/2001 20:02:00)
Sorry Sarge I see you are using on ODBC connection. I dont know from the infor whether you set up your database connection, or you are using FP2000? ODBC is a way of talking to a database. OLEDB is another way and is more recommended. ODBC may look like this : "DRIVER={Microsoft Access Driver (.mdb)}; DBQ=" & server.mappath(DatabaseFolder) OLEDB like this : "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & Server.Mappath(DatabaseFolder) This is used when manually coding asp. Otherwise, FP does it for you automaticlly ------------------ Spooky* "I am Spooky of Borg. Prepare to be assimilated, babycakes!" Subscribe to OutFront News Database / DRW Q & A The Spooky Login!

jsims -> RE: Access unstable? (3/8/2001 17:39:00)
Spooky -- I was intrigued by your recommendation of OLE DB instead of OBDC for managing a db connection. Do you need to make sure that your web provider supports this? Can you elect this type of connection in frontpage when you import an access database, or do you need to hand code the connection string on each new DRW page you create? If you can point us to any good backgrounders on doing this, that would be great. Thanks! Jim Sims jsims@policycom.com ------------------

Vince from Spain -> RE: Access unstable? (3/8/2001 18:11:00)
Here's an article I read a while back about why to use OLEDB as Spooky says, and what it is etc . . . http://www.4guysfromrolla.com/webtech/063099-1.shtml All the best Vince ------------------ Internet Business Solutions S.L.(Spain)

jsims -> RE: Access unstable? (3/12/2001 17:29:00)
Vince -- Thanks for the article on OLE DB. A dumb follow up question: Can I have FrontPage automatically use OLE DB instead of OBDC when creating pages that connect to my Access DB? Making sense of FP's "bot code" isn't easy, and I can't tell if it's using OLE DB. If I need to hand code the connection, will that mess up the code that FP generates using DRW? Thanks! Jim Sims jsims@policycom.com

Vince from Spain -> RE: Access unstable? (3/12/2001 18:42:00)
Hi Jim, as far as I know the answer is no . . . FP is going to use an ODBC connection by default. The actual connection is in the file global.asa which will be in the root of your web, but you may find that if you change it FP will change it back. If you decide to try, do back up first All the best Vince ------------------ Internet Business Solutions S.L.(Spain)

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.078125