I'm wondering if anyone else has experienced/fixed this.
No, but then I haven't tried to open dBase files with
Jet (i.e the MS Access database engine).
What is your connection string?
--
jc
Remove the -not from email
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\;Extended Properties=DBASE
III;Persist Security Info=False
I've also tried using BDE and ADO/ODBC. I can read other databases fine.
Greg
"Jeremy Collins" <jd.co...@ntlworld-not.com> wrote in message
news:411b2a9a$1...@newsgroups.borland.com...
> Here's my connection string
>
> Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\;Extended Properties=DBASE
> III;Persist Security Info=False
>
> I've also tried using BDE and ADO/ODBC. I can read other databases fine.
Don't know, sorry. I've seen connection string like this that
work with dbase IV (just a change in the Extended Properties).
Are you sure they're dBase III? Are you sure they're dBase at
all, and not Foxpro (a native FoxPro ADO provider exists,
which might be worth a try).
Are the database files complete and uncorrupted? (I.e can
you view them with another program?) If the BDE doesn't work
either I'd start to suspect the files themselves.
"Jeremy Collins" <jd.co...@ntlworld-not.com> wrote in message
news:411b...@newsgroups.borland.com...
> After installing Windows XP SP2, I get "Unexpected error from external
> database driver (15877)" when opening dbase files with ADO/jet.
>
> I'm wondering if anyone else has experienced/fixed this.
>
>
User submitted from AEWNET (http://www.aewnet.com/)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Xbase]
"BDE"=dword:00000002
BR, Xentrax
> After installing Windows XP SP2, I get "Unexpected error from external
> database driver (15877)" when opening dbase files with ADO/jet.
>
> I'm wondering if anyone else has experienced/fixed this.