[AccessD] Use if HIT ODBC/400 with Access 2003 - X Posted

Dan Waters dwaters at usinternet.com
Fri Apr 15 12:16:04 CDT 2005


Bud,

You didn't say if you actually have more than one index in the tables.  To
find out first put the table in Design view.  Then open the Index dialog box
by pushing the 'lightening bolt' button.  You can delete indexes from here.

To stop this from happening go to Tools|Options and click the Tables tab.
You'll see a field called AutoIndex on Import/Create.  Clear everything out
of this field.  If something in this field partially matches a name that
you've given to a field, then you'll automatically get an index on that
field.  Check Help to get the whole story. 

If you manually created an index for the same field, then you may have two
indexes with the same name.

Perhaps A97 did not have this AutoIndex feature.

HTH!

Dan Waters


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bud Goss
Sent: Friday, April 15, 2005 11:39 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Use if HIT ODBC/400 with Access 2003 - X Posted


Greetings from a long time ACCESSD lurker

 

I have used the HIT Software Inc with Access 97 databases to establish links
to our AS400 tables for quite a while.

 

When I attempt to use this software with an Access 2003 database to
establish an ODBC link to our AS400 ( for many - not all -  tables ) the
system will not create an ODBC link.

 

The message I get is Index already exists. Pressing Help gives the message
"Index already exists. (Error 3284)" You cannot have two indexes with the
same name in a table. Rename one of the indexes. 

 

But I can take the same table and establish an ODBC link with an Access 97
database.

 

I have attempted to do this on several Access 2003 databases ( Including a
new totaly empty Access 2003 database) and have the same problem.

 

I have sent HIT Software trace files for this situation.They have not yet
been able to determine the cause of this anomoly.

 

I suspect that the problem is in Access 2003 rather than with anything in
our AS400.

 

Has anyone else run into this problem? If so, do you have a solution.

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list