I'm trying the demo of the ODBC driver (latest build). I am on Vista Business and have a User DSN defined with a path to some sample DBISAM tables and am logged in as an Administrator.

Every time I connect to the database and try to import the tables I'm getting the above error message. Again, I can connect but can't pull the field definitions in. I am trying this also on Windows XP and Windows 7 and I get no such error (field list comes up fine). The tables are stored in a directory in the User's Documents folder and the Private dir is set similarly. I've uninstalled and reinstalled the driver, tried a System DSN, all with no luck.

Can anyone suggest anything to try?

Thanks.


Norman

Norman,

<< I'm trying the demo of the ODBC driver (latest build). I am on Vista
Business and have a User DSN defined with a path to some sample DBISAM
tables and am logged in as an Administrator.

Every time I connect to the database and try to import the tables I'm
getting the above error message. Again, I can connect but can't pull the
field definitions in. I am trying this also on Windows XP and Windows 7 and
I get no such error (field list comes up fine). The tables are stored in a
directory in the User's Documents folder and the Private dir is set
similarly. I've uninstalled and reinstalled the driver, tried a System DSN,
all with no luck. >>

What application are you using as the front-end to the ODBC driver ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim:

I was afraid you were going to ask that.

Actually, I'm using something called "Alpha5". It happens to work for me in certain projects and, as I said, I have little problem using it to create linked tables on my Windows XP and Windows 7 (64bit) computers. It's just on this d**n Vista machine (I'm considering upgrading to Windows 7 but that won't be for a while) that I'm having a problem.

I realize that you won't be able to test it being as Alpha5 is something people don't usually work with but I was hoping you might recognize the symptions.


Norman

"Tim Young [Elevate Software]" wrote:

Norman,



What application are you using as the front-end to the ODBC driver ?

Norman,

<< Actually, I'm using something called "Alpha5". It happens to work for me
in certain projects and, as I said, I have little problem using it to create
linked tables on my Windows XP and Windows 7 (64bit) computers. It's just on
this d**n Vista machine (I'm considering upgrading to Windows 7 but that
won't be for a while) that I'm having a problem.

I realize that you won't be able to test it being as Alpha5 is something
people don't usually work with but I was hoping you might recognize the
symptions. >>

Actually, I've worked with the Alpha 5 developers on getting EDB's ODBC
Driver to work with A5, and we have other EDB customers using A5 with the
ODBC driver.

If you want to send me your database (table files, and catalog also) along
with the steps that you're trying to perform in A5, I can try it here and
see what the problem is.

--
Tim Young
Elevate Software
www.elevatesoft.com

<<Actually, I've worked with the Alpha 5 developers on getting EDB's ODBC
Driver to work with A5, and we have other EDB customers using A5 with the
ODBC driver.

If you want to send me your database (table files, and catalog also) along
with the steps that you're trying to perform in A5, I can try it here and
see what the problem is.>>

Well, ain't that a kick in the head.

I was going to ask you what catalog you were referring to but let me wait until I try upgrading the computer to Windows 7. If the problem goes away then there's no need to waste time on it.

Thanks for the response.


Norman

Tim:

I've upgraded my machine to Windows 7 Pro and am still getting the error.

I define a datasource using the DBISAM ODBC driver and can connect to it successfully when building a connection string in Alpha 5. However, when I try to create an Active Link table, I get the error when Alpha 5 tries to retrieve the list of tables (it finds the tables but can't get the field list, Database API specific error). BTW, this occurs whether I'm doing it logged in as an Administrator or as a Standard User. The Private Directory in the DataSource is set to a subdirectory of the C:\Users\Limited User directory, where "Limited User" is my logon name.

As I say, all this works fine on my other machine (one is actually Windows 7 as well, so who knows). However, I'm not sure what you mean by the catalog. I can certainly send you the table(s) but what else, specifically, do you need in order to be able to test this out?

Thanks.



Norman
<<Actually, I've worked with the Alpha 5 developers on getting EDB's ODBC
Driver to work with A5, and we have other EDB customers using A5 with the
ODBC driver.

If you want to send me your database (table files, and catalog also) along
with the steps that you're trying to perform in A5, I can try it here and
see what the problem is.>>

Norman,

<< I define a datasource using the DBISAM ODBC driver and can connect to it
successfully when building a connection string in Alpha 5. However, when I
try to create an Active Link table, I get the error when Alpha 5 tries to
retrieve the list of tables (it finds the tables but can't get the field
list, Database API specific error). BTW, this occurs whether I'm doing it
logged in as an Administrator or as a Standard User. The Private Directory
in the DataSource is set to a subdirectory of the C:\Users\Limited User
directory, where "Limited User" is my logon name.

As I say, all this works fine on my other machine (one is actually Windows 7
as well, so who knows). However, I'm not sure what you mean by the catalog.
I can certainly send you the table(s) but what else, specifically, do you
need in order to be able to test this out? >>

Sorry about that - the catalog is part of EDB, and I got my products mixed
up there.

If you can just send me the table files, that will be great.

--
Tim Young
Elevate Software
www.elevatesoft.com

No problem, Tim. Actually, the issue resolved itself after I installed the latest Alpha5 patch.

Ain't that always the way?

Now on to the next problem, lying out there in wait for me.

Thanks again for the prompt responses.




Norman

"Tim Young [Elevate Software]" wrote:

Norman,

<< I define a datasource using the DBISAM ODBC driver and can connect to it
successfully when building a connection string in Alpha 5. However, when I
try to create an Active Link table, I get the error when Alpha 5 tries to
retrieve the list of tables (it finds the tables but can't get the field
list, Database API specific error). BTW, this occurs whether I'm doing it
logged in as an Administrator or as a Standard User. The Private Directory
in the DataSource is set to a subdirectory of the C:\Users\Limited User
directory, where "Limited User" is my logon name.

As I say, all this works fine on my other machine (one is actually Windows 7
as well, so who knows). However, I'm not sure what you mean by the catalog.
I can certainly send you the table(s) but what else, specifically, do you
need in order to be able to test this out? >>

Sorry about that - the catalog is part of EDB, and I got my products mixed
up there.

If you can just send me the table files, that will be great.

--
Tim Young
Elevate Software
www.elevatesoft.com

Norman,

<< No problem, Tim. Actually, the issue resolved itself after I installed
the latest Alpha5 patch. >>

Great, I'm glad that you fixed the issue.

<< Ain't that always the way? >>

Well, it is when you're having a *good* week.

--
Tim Young
Elevate Software
www.elevatesoft.com