I am having a problem with the DBA tables for BKARINV.B and was hoping for some advice.  I am a complete ODBC novice.
 
We use Pervasive 2000i with ISTECH 1/12/06. We have been using DBA since 1996 or so.
 
Our UPS system (Worldship 8.0) cannot seem to interface with the 2 extra address fields in DBA due to the spaces in the table name (we import address information from the Sales Order).  Everything else imports just fine.
 
I am wondering if there is some utility I can run to remove the spaces from the table names of BKARINV.B so that we can interface properly, or some way the table can be edited to remove the spaces (or insert underscores in the place of spaces).
 
I tried recreating the DDF files but this did not help the situation.
 
I would greatly appreciate anyone's advice on this issue.

I'm not sure how you setup your ODBC, but I believe the fields that you are having trouble with are the Array fields. Fields like ship[1], ship[2], etc.  I found that I must setup my ODBC and be sure to check that box that says "Use OEM/ANSI Conversion".  This will then pull the array fields into the ODBC as ship_1, ship_2.  Also, I found that if I set one up as unchecked it would not simply let me check it later. I had to delete it and go through the setup again.
 
Good luck,

Unfortunately, it did not work with creating a new system DSN with OEM/ANSI box checked.
 
We interface fine with the first address line and all other data, but the BKAR_INV_SHPA2[ 1] and BKAR_INV_SHPA2[ 1]  lines cannot be connected to the UPS database.  My hypothesis is the space in the array name.  The array title I have listed is exactly as it appears in DBA.
 
Do others have these same array names and have a workaround?
 
If I can get this fixed it would be great, as it is almost impossible to fit all address information on one line (the first one!) so the import works properly.

Maybe this is a question for Lynn:
 
When I go to the Pervasive Control Panel and open the filename BKARINV.B, the array names for the second 2 lines of the ship-to address in Sales Orders appear as:
 
BKAR_INV_SHPA2[ 1]
BKAR_INV_SHPA2[ 2]  
 
This space in the field name is not allowing proper interfacing with UPS software.  There are other field names in the BKARINV.B file that also have spaces in them, but that is not important for this application (although it may be in the future).
 
I have tried creating a new System DSN using the OEM/ANSI conversion box checked as rmh148 suggested but the spaces in the filenames still appear, and the mapping does not work.  The spaces also appear in the Pervasive Control Panel if I click on the array name.  
 
Could this be because we have a very old DBA installation (for instance, our data files .B, run files, and rtms are all in the DBAMFG directory)?
 
I would certainly be willing to pay $$ to get this issue resolved.  We have had more than one shipping error due to this issue.

For what it's worth, here's a screenshot of the field mapping from our UPS installation.  Note this is Worldship v7.
 

 
 

Thank you everyone for your help.
 
I should have taken rmh148's advice one step further and actually recreate the ddf files after checking the OEM/ANSI box.
 
Now that I have done so the file can be imported properly into UPS.

Hi Folks,
 
We're taking steps to implement this for UPS and FexEx.
 
I don't know much about how this actually works once you set it up, so can anyone enlighten me please so I have a better idea.
 
Also, is the setup essentially the same with FedEx?
 
Thanks,
 
Val

The sales order is what we use as the Primary Key field. I chose not to write back the tracking $ to EVO. It uses the notes field but doesn't add like UPS or Fed-Ex as a reference. My customers would get a little confused. Both UPS and Fed-Ex are a bit of a pain to get set-up and they are not even remotely similar in use or set-up. Once up and running, they are great. I think UPS did a better job than Fed-Ex in a lot of way's.
 
 
John