Access ODBC connection to Customer Table

You have to create a view and then connect to it. For example:

Create View odbcuser.Customer_view As SELECT * From pub.Customer;
grant select on odbcuser.Customer_view to odbcuser;
Commit;


Adam Gwizdz
Manager, Corporate IT Systems
Main Tape Company
1 Capital Drive, Suite 101
Cranbury, NJ 08512
(800)718-8273 x332



_____

From: Dan Tisone [mailto:dan.tisone@...]
Sent: Tuesday, August 29, 2006 4:30 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Access ODBC connection to Customer Table



Hello all -

I am trying to connect via Access to Customer table to do some minor
data manipulation. When I attempt to link the Customer table, I get an
error:

"The operation failed. There are too many indexes on table
'PUB_CUSTOMER'. Delete some of the indexes on the table and try the
operation again."

Has anyone overcome connecting to the Customer table from Access or have
any ideas on how to circumvent this problem?

Thanks,

Dan Tisone

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]
Hello all -



I am trying to connect via Access to Customer table to do some minor
data manipulation. When I attempt to link the Customer table, I get an
error:



"The operation failed. There are too many indexes on table
'PUB_CUSTOMER'. Delete some of the indexes on the table and try the
operation again."



Has anyone overcome connecting to the Customer table from Access or have
any ideas on how to circumvent this problem?



Thanks,



Dan Tisone











[Non-text portions of this message have been removed]
> "The operation failed. There are too many indexes on table
> 'PUB_CUSTOMER'. Delete some of the indexes on the table and try the
> operation again."

If you search the archive of this list (and wade through the untrimmed
messages) you will find that the answer is to create a view and the link to
that view.

Mark W.

P.S. The links to this group online are listed below.
Open SQL Eplorer, connect to your DB and then type:

"Create view custview as select * from PUB.Customer;" then click the
run button

Then type:

"Commit; " Then click the run button



CustView is a name that I use, you can call the view by any name you
wish.



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Dan Tisone
Sent: Tuesday, August 29, 2006 4:30 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Access ODBC connection to Customer Table



Hello all -

I am trying to connect via Access to Customer table to do some minor
data manipulation. When I attempt to link the Customer table, I get an
error:

"The operation failed. There are too many indexes on table
'PUB_CUSTOMER'. Delete some of the indexes on the table and try the
operation again."

Has anyone overcome connecting to the Customer table from Access or have
any ideas on how to circumvent this problem?

Thanks,

Dan Tisone

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
Dan

Access only supports upto 32 indexes, so tables that have more need to accessed indirectly.

You need to either create a progress view using the data administrator tool, but you can only do this in single user mode.

or

You could just create a SQL Pass-through query in Access and then read from that instead. This way you do not need the database to be in single user mode.

Regards

Gary Parfrey
Dot Net IT Limited

________________________________

From: vantage@yahoogroups.com on behalf of Dan Tisone
Sent: Tue 29/08/2006 21:30
To: vantage@yahoogroups.com
Subject: [Vantage] Access ODBC connection to Customer Table



Hello all -

I am trying to connect via Access to Customer table to do some minor
data manipulation. When I attempt to link the Customer table, I get an
error:

"The operation failed. There are too many indexes on table
'PUB_CUSTOMER'. Delete some of the indexes on the table and try the
operation again."

Has anyone overcome connecting to the Customer table from Access or have
any ideas on how to circumvent this problem?

Thanks,

Dan Tisone

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]