Sarah,
I'm wondering if you've found a way around this problem yet. I too
use a lot of ODBC to Access applications and the customer table is
heavily involved. I'm still on 5.0 for the time being, but may be
forced to move forward soon. While working with Virginia from
support on a different ODBC problem, I mentioned the problem you were
having. This was her reply.
Yes, it is true that Access is not robust enough to handle the
indexes in the Customer table. There are a couple of ways around the
issue:
1. Use SQL
2. Follow the instructions in the attached document to create a view
of the customer table - then use Access to connect to this view.
Virginia
I have the instructions for creating the view if you need it, e-mail
me off list and I will send it to you. I'd really like to know how
your going to work around this problem.
Thanks,
Brian Stenglein
Clow Stamping Co.
I'm wondering if you've found a way around this problem yet. I too
use a lot of ODBC to Access applications and the customer table is
heavily involved. I'm still on 5.0 for the time being, but may be
forced to move forward soon. While working with Virginia from
support on a different ODBC problem, I mentioned the problem you were
having. This was her reply.
Yes, it is true that Access is not robust enough to handle the
indexes in the Customer table. There are a couple of ways around the
issue:
1. Use SQL
2. Follow the instructions in the attached document to create a view
of the customer table - then use Access to connect to this view.
Virginia
I have the instructions for creating the view if you need it, e-mail
me off list and I will send it to you. I'd really like to know how
your going to work around this problem.
Thanks,
Brian Stenglein
Clow Stamping Co.
--- In vantage@yahoogroups.com, sarah.vareschi@n... wrote:
>
> I am attempting to convert my ODBC reports from Vantage 5.0 to
Vantage 5.2.
> I am using Microsoft Access 2002 and the Vantage 5.2 driver (Merant
3.6
> SQL), with the progress database.
>
> I am able to reconnect all my tables, except the 'Customer' table.
When I
> try to link from Access to the Vantage 5.2 Customer table, I get the
> following error: damsgtoomanyindexesm "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. (Error 3626)"
>
> The description in Access help of the error is as follows: "A
table in a
> Microsoft Jet database <JavaScript:hhobj_1.Click()> can have no
more than
> 32 indexes <JavaScript:hhobj_2.Click()> . Delete one or more
indexes from
> the named table and try the operation again."
>
> I do not know how to proceed, does anyone else know how to fix this?
>
>
> [Non-text portions of this message have been removed]