ASP to Access 97 mdb under MDAC 2.8

If I have a web site using ASP 3.0 and MS Access and hosted on a
server with MDAC 2.7/2.8 installed, does it make any difference
whether the mdb is an Access 97 one or an Access 2000 one? I only have
Access 97. The hosting company intimated that I should seriously
consider converting the mdb to Access 2000. Could I do that with ADO?
I have VB6.

MM

re: ASP to Access 97 mdb under MDAC 2.8

On Wed, 04 May 2005 17:58:20 +0100, MM <kylix_is@yahoo.co.uk> wrote:
[color=blue]
>If I have a web site using ASP 3.0 and MS Access and hosted on a
>server with MDAC 2.7/2.8 installed, does it make any difference
>whether the mdb is an Access 97 one or an Access 2000 one? I only have
>Access 97. The hosting company intimated that I should seriously
>consider converting the mdb to Access 2000. Could I do that with ADO?
>I have VB6.[/color]

Ah, it looks like Visual Data Manager in VB6 might come to my aid
here. I can create a version 2.0 mdb, then import the Access 97
tables, probably. The mdb stores only tables, no code, no macros, no
queries. It is -just- a database. Has anyone tried converting this
way, using VisData/VB6?

MM

re: ASP to Access 97 mdb under MDAC 2.8

On Wed, 04 May 2005 18:08:35 +0100, MM <kylix_is@yahoo.co.uk> wrote:
[color=blue]
>On Wed, 04 May 2005 17:58:20 +0100, MM <kylix_is@yahoo.co.uk> wrote:
>[color=green]
>>If I have a web site using ASP 3.0 and MS Access and hosted on a
>>server with MDAC 2.7/2.8 installed, does it make any difference
>>whether the mdb is an Access 97 one or an Access 2000 one? I only have
>>Access 97. The hosting company intimated that I should seriously
>>consider converting the mdb to Access 2000. Could I do that with ADO?
>>I have VB6.[/color]
>
>Ah, it looks like Visual Data Manager in VB6 might come to my aid
>here. I can create a version 2.0 mdb, then import the Access 97
>tables, probably. The mdb stores only tables, no code, no macros, no
>queries. It is -just- a database. Has anyone tried converting this
>way, using VisData/VB6?[/color]

Oops! That version 2.0 malarkey, they don't mean Access 2000, do they!
I'd forgotten all about Access 2.0. Oh well, back to the drawing
board. Has anyone written a utility to convert 97 to 2K?

MM

re: ASP to Access 97 mdb under MDAC 2.8

On Wed, 04 May 2005 18:13:02 +0100, MM <kylix_is@yahoo.co.uk> wrote:
[color=blue]
>On Wed, 04 May 2005 18:08:35 +0100, MM <kylix_is@yahoo.co.uk> wrote:
>[color=green]
>>On Wed, 04 May 2005 17:58:20 +0100, MM <kylix_is@yahoo.co.uk> wrote:
>>[color=darkred]
>>>If I have a web site using ASP 3.0 and MS Access and hosted on a
>>>server with MDAC 2.7/2.8 installed, does it make any difference
>>>whether the mdb is an Access 97 one or an Access 2000 one? I only have
>>>Access 97. The hosting company intimated that I should seriously
>>>consider converting the mdb to Access 2000. Could I do that with ADO?
>>>I have VB6.[/color]
>>
>>Ah, it looks like Visual Data Manager in VB6 might come to my aid
>>here. I can create a version 2.0 mdb, then import the Access 97
>>tables, probably. The mdb stores only tables, no code, no macros, no
>>queries. It is -just- a database. Has anyone tried converting this
>>way, using VisData/VB6?[/color]
>
>Oops! That version 2.0 malarkey, they don't mean Access 2000, do they!
>I'd forgotten all about Access 2.0. Oh well, back to the drawing
>board. Has anyone written a utility to convert 97 to 2K?[/color]

Fixed it! I referred to Larry Rebich's article "DAO 3.60 and Jet 4 -
July 1999 and December 2000" to create an Access 2000 mdb in VB6.
http://www.buygold.net/v02n12/v02n12.html

Then I followed the mods in:
How To Modify the Visual Data Manager (VISDATA) to Work with Access
2000 Databases
KB Q252438

Finally, I recompiled visdata, opened a newly created Access 2000 mdb,
and imported the tables from my Access 97 mdb.

MM

re: ASP to Access 97 mdb under MDAC 2.8

MM <kylix_is@yahoo.co.uk> wrote in
news:cfvh71decsflsv4i6qprp61bo3njvjborv@4ax.com:
[color=blue]
> If I have a web site using ASP 3.0 and MS Access and hosted on a
> server with MDAC 2.7/2.8 installed, does it make any difference
> whether the mdb is an Access 97 one or an Access 2000 one? I only
> have Access 97. The hosting company intimated that I should
> seriously consider converting the mdb to Access 2000. Could I do
> that with ADO? I have VB6.[/color]

Your ISP is run by ignorant people.

If the MDAC installation is Jet 4, it can deal perfectly well with a
Jet 3.5 database (an Access database is a special kind of Jet
database with objects of its own that Jet itself knows nothing
about; on a website using ASP, you're not using any of the Access
properties of the MDB, so you're not really using an "Access"
database at all, just a Jet db).

You don't have any need to convert the db to Jet 3.5.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

re: ASP to Access 97 mdb under MDAC 2.8

On Thu, 05 May 2005 00:41:11 GMT, "David W. Fenton"
<dXXXfenton@bway.net.invalid> wrote:
[color=blue]
>MM <kylix_is@yahoo.co.uk> wrote in
>news:cfvh71decsflsv4i6qprp61bo3njvjborv@4ax.com :
>[color=green]
>> If I have a web site using ASP 3.0 and MS Access and hosted on a
>> server with MDAC 2.7/2.8 installed, does it make any difference
>> whether the mdb is an Access 97 one or an Access 2000 one? I only
>> have Access 97. The hosting company intimated that I should
>> seriously consider converting the mdb to Access 2000. Could I do
>> that with ADO? I have VB6.[/color]
>
>Your ISP is run by ignorant people.
>
>If the MDAC installation is Jet 4, it can deal perfectly well with a
>Jet 3.5 database (an Access database is a special kind of Jet
>database with objects of its own that Jet itself knows nothing
>about; on a website using ASP, you're not using any of the Access
>properties of the MDB, so you're not really using an "Access"
>database at all, just a Jet db).
>
>You don't have any need to convert the db to Jet 3.5.[/color]

Thanks, David. The current Access 97 mdb works fine on Brinkster,
using the Jet.OLEDB.4.0 provider. The bloke reckoned there were 'big
locking issues' with Access 97, but I have used it to build and
maintain many databases for years without any trouble.

MM

re: ASP to Access 97 mdb under MDAC 2.8

MM <kylix_is@yahoo.co.uk> wrote in
news:n49k71pfmn2sll681v614gcn5qhtbmekus@4ax.com:
[color=blue]
> On Thu, 05 May 2005 00:41:11 GMT, "David W. Fenton"
><dXXXfenton@bway.net.invalid> wrote:
>[color=green]
>>MM <kylix_is@yahoo.co.uk> wrote in
>>news:cfvh71decsflsv4i6qprp61bo3njvjborv@4ax.co m:
>>[color=darkred]
>>> If I have a web site using ASP 3.0 and MS Access and hosted on a
>>> server with MDAC 2.7/2.8 installed, does it make any difference
>>> whether the mdb is an Access 97 one or an Access 2000 one? I
>>> only have Access 97. The hosting company intimated that I should
>>> seriously consider converting the mdb to Access 2000. Could I do
>>> that with ADO? I have VB6.[/color]
>>
>>Your ISP is run by ignorant people.
>>
>>If the MDAC installation is Jet 4, it can deal perfectly well with
>>a Jet 3.5 database (an Access database is a special kind of Jet
>>database with objects of its own that Jet itself knows nothing
>>about; on a website using ASP, you're not using any of the Access
>>properties of the MDB, so you're not really using an "Access"
>>database at all, just a Jet db).
>>
>>You don't have any need to convert the db to Jet 3.5.[/color]
>
> Thanks, David. The current Access 97 mdb works fine on Brinkster,
> using the Jet.OLEDB.4.0 provider. The bloke reckoned there were
> 'big locking issues' with Access 97, . . .[/color]

Why in the world should there be any at all? Jet 4 record locking is
a joke and nobody that I know actually uses it (it adds so much
overhead that it drags everything to a halt).

Jet 4 and Jet 3.5 are really pretty much identical in real-world
usage in regard to record-locking issues, even if Jet 4 is supposed
to be improved in that regard.
[color=blue]
> . . . but I have used it to build and
> maintain many databases for years without any trouble.[/color]

ISP's generally know absolutely zilch about Access and Jet. The hard
part is convincing them of their ignorance, something of a
delicately diplomatic task.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc