Pervasive ODBC via MS Access 1

[Darrylles]

Hi,

Win XP, Access 2000, Pervasive 2000i

I'm attemptiing to link to Pervasive tables through MS Access via the Pervasive ODBC driver.

The tables belong to the company ERP system, which does not have problems.

I'm using a Machine DSN.
This works fine, except for one particular table (typically, it's the most important table). When I attempt to link to this particular table I get:

" 'Default_Method_(Eng.' is not a valid name. Make sure that it does not contain invalid characters or punctuation and that it is not too long. "

I don't know what this object is, but it does contain invalid characters (the left bracket, and the period).

As I have said, this table is used by the ERP system, and therefore I can only surmise that the ODBC driver is somehow at fault here.

Any ideas much appreciated.

ATB

Darrylle





Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@yahoo.co.uk

 

[mirtheil]

That's probably a field in the table. Can you access that table through another ODBC application (PErvasive COntrol Center, Excel/MS Query, ODBC Test, etc)?
WHat happens if you use a SQL Passthrough Query rather than link the table?

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.

http://www.mirtheil.com

 

[Darrylles]

Hi,

Thanks for responding - sorry I took a while to get back.

I've found out that this IS a field in a table (I can't believe that someone has included special characters in a name).

I can connect via Crystal Reports and the ERP system accesses it, but obviously the MS Access ODBC driver does not like the special characters (as I would normally expect).

I've not used a passthrough query before, does this bypass the ODBC driver?

Regards,

Darrylle


Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@yahoo.co.uk

 

[mirtheil]

SQL Passthrough doesn't bypass ODBC but bypasses Access and goes straight to the ODBC driver.

You can try to delimit the invalid field name. Pervasive uses double quote ("Default_Method_(Eng.") to delimit field names.

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.

http://www.mirtheil.com