I seem to be having a problem accessing my BKICMSTR table through my DBA connection manager setup since we have installed the 2/14/07 update.  All other tables seem to open fine.
 
I am getting: ODBC Call Failed [Pervasive][ODBC Client Interface]Numeric Value out of range. (#0) when I try to view the BKICMSTR table.
 
I thought this might be because we had set our SD-Q to Require Category codes, but did not have them set up before doing this.  Is this a situation where I need to 'reindex the file' - will this help?
 
Lynn has said we have a program called NZIndex - is this how you reindex a file?
 
Anybody have any ideas on how to help me.  I do not want to use the MTICMSTR file because it does not contain the category codes I need for sorting.  
 
Thanks,
Robin

Kelloggs,
 
Thank you for your prompt reply.  I ran both the UT-C on BKICMSTR, and I've run UT-K-I.
 
When I ran UT-K-I, it ran through 23 of 23 files, then hung up at the end of 77 of 77 files, and would not exit.  I had to force an End Task, and reboot the server.  
 
Neither of the procedures has helped completely although I have noticed a change in how the data is acting.  Now I seem to be able to look at the data within Access, but as soon as I want to export the data, it hangs on the ODBC failed error again.
 
My next step is going to be to try to recreate a new Pervasive Database Engine...do you have any other ideas?
 
Thanks,
Robin

Funny you should mention that - yes I have, and I run into the following error:
 
Btrieve Error - V:\Default\File.ddf - 5.
 
I had sent this message to Bill Rouser, who suggested I use a global.exe file to find a duplicate file.  I ran this file, and it looked like it came back with something similar to MEATTRIB, but Bill did not explain how to use the program he sent, so I am back to being lost.
 
I find that having our data files stored on a different drive letter creates a lot of havoc in my life.  Our DBAMFG files are stored on our U: drive, and our Default folder is stored on V:.  Can you shed any more light on this situation?
 
Thanks again,
Robin

I received that Btrieve Error during the ODBCDDF process, I said ok, then it kept going with what it was doing.
 
DBA Connection Manager is a program I downloaded to link my tables from DBA to MS Access 2003.

Sorry - don't understand what you mean - did I try what - rebooting?  Yes.
 
What about my inability to complete the ODBCDDF.run without an error?

Refresh my understanding, the ODBC DDF files are stored in the Default folder?  and if I rename the something like file.old - I can then create new DDF files?
 
I have two default folders, I am assuming you mean my actual current data file Default folder that is stored on a different drive?
 
Thanks again for your help....I am trying to contact mwaccounting for help as well....Robin

Kevin,
 
I just tried this - renaming the FILE.DDF in my Default folder where my BXX files are to File-old.ddf and reran ODBCDDF - I still get the same error - Btrieve Error - V:\Default\File.ddf - 5.  
 
You wrote below to use ODBCDDF.RUN - when I type that in I am told I do not have this program.  
 
Are these two different actions?
 
Robin

I can.  Ran the update and it trashed one of the indexes in the BKIC_MSTR.  Ran the Pervasive Rebuild utility at Lynn's suggestion then the ODBCDDF.run and it solved the the index corruption and our Access ODBC link.
 
John