On 15 May 2005 18:56:02 -0500,
d.schofieldREMOVE@blueyonder.co.uk
(David Schofield) wrote:
[color=blue]
>On Sun, 15 May 2005 23:23:41 +0100, MM <kylix_is@yahoo.co.uk> wrote:
>[color=green]
>>On Sun, 15 May 2005 16:16:48 +0200, "Arno R"
>><arraNOcomSPAM@tiscali.nl> wrote:
>>[color=darkred]
>>>"MM" <kylix_is@yahoo.co.uk> schreef in bericht news:ojle81t7h43cb3vp0ugud1aninrpp0drqt@4ax.com...
>>>> And Access 2000 et seq 32 bit?
>>>>
>>>> MM
>>>
>>>Access 97 is 32 bit
>>>Access 2.0 was the last 16 bit version.[/color]
>>
>>Oh. The reason I asked was that a web hosting company I was
>>considering for ASP/Access hosting stated that they didn't recommend
>>Access 97 databases, but only Access 2000 or later. The reason, they
>>said, was that Access 97 mdb's may produce the error: "Cannot open
>>database '(unknown)'. It may not be a database that your application
>>recognizes, or the file may be corrupt."
>>
>>Now this is exactly the error that I have been having for months on
>>one of the freebie hosting sites. I was at my wits' end, until I saw
>>this advice. Then I upated the mdb to Access 2000 (Jet 4.0?) and since
>>then the problem has disappeared on the freebie site.
>>
>>So, having used Access 97 for years without a problem in standalone
>>apps, accessing mdb's from VB6, I wonder why there is this apparent
>>problem when in an ASP/IIS environment and why the Access 2000 version
>>should fix it? Weird. I thought maybe it's because the Access 97
>>version is 16-bit. Maybe it's that that it doesn't like. Must be
>>something else, though.
>>
>>MM[/color]
>Hi
>This is what Streamline.net say:
>"You should use only Access 2000 or higher databases. If you use
>Access 97 you may receive the following error:-
>[Microsoft][ODBC Microsoft Access Driver] Cannot open database
>'(unknown)'. It may not be a database that your application
>recognizes, or the file may be corrupt.
>This is due to an issue in MDAC 2.5 and greater and is only resolved
>by using a newer version of Access."[/color]
Yes, that is exactly the same wording as on the Asp-Host site.
Certainly, since upgrading the mdb to 2000 this problem seems to have
disappeared. I wonder what the 'issue' is. Access 97 versioned mdb's
work fine through VB6.
MM