Access is the devil!

Here is my situation...
I have been running office 2000 on my computer and all of my applications create databases at runtime using DAO. Now I have an existing Access database that is WAY to vast to create through my application, so I need to go into it and make alterations to it, yet still be able to access it. Last time I checked, it was not possible to hook up to an Access 2000 database in VB. I have uninstalled Office 2000, and installed Office 97... when I try to run Access, it tells me that there is no license for it on my computer. Does anyone know how I can either remedy this, or somehow access MS Access 2000 databases in Visual Basic?

thanks a million!



çentipede

cent1pede@hotmail.com

Attached file will make Access97 to run again on your computer. It is known Microsoft bug.

wow cool, thanks. do i just run it from any location on my computer? or does it have to be in a specific dir, etc?

çentipede

cent1pede@hotmail.com

I just looked on msdn, found the answer...

install office 2000.
to install access 97, do the following...

in the fonts dir, find Hatten.ttf (hattenschweiler..something)
rename it Hatten.sav (or sumthing)
find MSAccess.exe, rename something like MSAccess.2k

install access 97, then restore the names of the two files to their original names.

çentipede

cent1pede@hotmail.com

You can continue to revert to old techology if you want, but the procedure for attaching to an Access2000 database is the same as Access97. Although I've never tried to use DAO to do it but that's mainly because it's a superceded technology. When using ADO the only difference is that the provider should be the Jet 4.0 and not the Jet 3.5.

You can also create and modify databases ie. Jet databases, using ADOX instead of DAO.

problem w/ ADO, is you cannot change the database path at run time, can you?

antiquated or not, Access 97 does the trick for the applications I am making, just because we all run CDR or DVD does not mean that we need to obliterate the floppy from the face of the Earth.

Thanks for the input. I HAVE been meaning to expand my database horizons, however, i have been charmed by other areas of VB programming, perhaps now that my feverish coding frenzy is slowing to human levels again, i will find more time for the tedious necessities.

çentipede

cent1pede@hotmail.com

When you say 'change the database path at runtime' what do you actually mean? eg. moving the database or connecting to a different database?

I like to allow the user to either, create multiple databases they can use with my applications, or give them the opportunity to have my application recreate the DB if it gets damaged, or deleted. So I need to be able to hook up to different databases at runtime, and store their paths in ini files, so when the user loads my app, it checks for the DB path in the ini file, and hooks up to that database. What little I have read bout ADO has said that the DB path MUST be set at design time. unfortunately I am just now getting VERY comfortable with DAO. I have no idea how to create, hook up to, modify DB's using ADO. *yet* lol.


thanks


çentipede

cent1pede@hotmail.com

Perhaps when using a DataControl it must be set a design time. But with the ADODB.Connection object you can set it at any time. The connection is determined by the ConnectionString that you give the object. You can alter that at runtime. You can even connect to two databases simultaneously if you have two Connection objects.

You can't create/modify databases with ADO. If you are using a Jet database however, you can create/modify databases with ADOX.

Out of interest, where did you read that you have to set the database path at design time?

Q...