Issue importing a linked table into Access via ODBC connection to iSeries

Hi All,

My organization recently migrated our iSeries to a virtualized one in another location.  With this, I had to create a new ODBC connection to this system within Access to create a linked table,  I have an issue creating a link to one table in the WHOLE database.  The error I'm receiving is:  Invalid field definition 'MBFI' in definition of index or relationship.  Now I'm trying a fresh Access database and I'm still getting this error.  The reference field is only the beginning of a column name, it isn't the whole column name.  Anyone have any suggestion on how I might be able to fix this?
LVL 1
Anthony6890Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gary PattersonVP Technology / Senior Consultant Commented:
Can you publish the layout for the offending table from the iSeries side, including indexes and constraints?  Something is funky in one of your indexes that is causing Access to choke.

What version of Access are you running, and what version of MDAC?
0
Anthony6890Author Commented:
Sure I could, but I'm no so versed in getting in all the information.  What's the best way of getting the layout to you?  I'm running Access 2010 and I don't know the version of MDAC as of right now.
0
Gary PattersonVP Technology / Senior Consultant Commented:
IBM i DB2 metadata can be found in SYSTABLES, SYSCOLUMNS, SYSINDEXES, SYSKEYS, etc in library QSYS2.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Anthony6890Author Commented:
I need a little more help.  I've found the qsys2, but I can't find the rest of sys items you list above other than sysindexes.
0
Gary PattersonVP Technology / Senior Consultant Commented:
How did you find SYSINDEXES?
0
Anthony6890Author Commented:
I did strpdm from the command line and found it by looking at objects.
0
Anthony6890Author Commented:
Gary,

We solved the issue.  We did some testing and copied the file to another library and I was  then able to import the linked table in Access.  So what we did was copy the problem physical file, then deleted the old one, and renamed the copied file back to the original name.  We then recompiled all the logicals that were over the physical file and everything works correctly.  I don't know exactly how it worked; however, it did fix the issue.  

I thank you for your help.  

-Anthony
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Anthony6890Author Commented:
The problem identified was correct; however, I was able to solve the issue using my own process but the logic offered.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IBM System i

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.