|
| The AccuTerm forum has moved. Go to community.rocketsoftware.com to register for the new Rocket forum. |
|
Post Reply 
|
| Author | |
Sueglo 
Newbie 
Joined: January 11 2007 Location: United States Status: Offline Points: 8 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: ftd errmsg using Access mdb extensionPosted: February 05 2008 at 4:10am |
|
Hi all,
I had to start using access for the first time instead of excel when doing an ftd.
This proc always worked fine with excel, but for some reason, all I did was change the file to an access file, and it says that it converts the file, and then says that there is an invalid table name.
Is there a limit to the name size of the tables? Like before windows 95 when you could only have an 8 char file name? Is that what's wrong here?
If anyone can shed some light, I would appreciate it.
Thanks,
Susan
I get a weird errmsg when the transfer is happening. It says:
FTD
S K POLICIES M:\OVERN\COMPOLICIES.MDB!COMPOLICIES!
CLIENT.CODE NAME SERV PROD STREET1 POLNO PHONE DIV CITY STATE ZIP CONO DIV DEPT PREM COMM COV EFF.DATE EXP.DATE CAT Y N AccuTerm Data Transfer Utility Converting COMPOLICIES.MDB!COMPOLICIES! to MS Access file format... done. Transfer status: Invalid table name - COMPOLICIES
Transferred 12491 items, 1999765 bytes. |
|
|
Susan
|
|
 |
|
|
jgold
Moderator Group 
Moderator Joined: December 29 2003 Location: United States Status: Offline Points: 48 |
Post Options
Thanks(0)
Quote Reply
Posted: February 06 2008 at 3:48am |
|
Hi Susan,
I tried downloading some data to a COMPOLICIES table but was unable to duplicate the problem. I didn't have the same field names as you but I wouldn't think that would be the problem. I also tried creating a table with your field names to see if that might be triggering an error but they all seem legal. (The conversion changes all "."s to "_" so if you try to create the table yourself, you'll have to do that manually). So it doesn't look like there's anything wrong with your table or field names. You'll have to try some things to trace it down. You can create the table with those fields manually in Access to see if your version has any problems there. If that works, the problem is probably in the data. Try sending fewer fields or select a few test records instead of the entire file to see if some record is causing the problem. |
|
|
|
|
Sueglo
Newbie
Joined: January 11 2007 Location: United States Status: Offline Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: February 06 2008 at 4:00am |
|
ok, I see what you are saying, but I don't understand why it works in excel, but not access.
What typically causes this invalid table name errmsg, and why does it say transferred, when the data doesn't transfer? Does Access scan for any "dirty data", and reject it as opposed to excel just accepting it?
Transfer status: Invalid table name - COMPOLICIES Transferred 12491 items, 1999765 bytes. |
|
|
Susan
|
|
|
|
|
bneylon
Senior Member 
Joined: March 03 2004 Location: United States Status: Offline Points: 103 |
Post Options
Thanks(0)
Quote Reply
Posted: February 06 2008 at 6:22am |
|
I get that error when I use a dictionary item with a value mark in header(<4> in UD)
Bruce |
|
|
|
|
jgold
Moderator Group
Moderator Joined: December 29 2003 Location: United States Status: Offline Points: 48 |
Post Options
Thanks(0)
Quote Reply
Posted: February 06 2008 at 7:21am |
|
Excel and Access are two completely different animals. Excel can take any value in any cell where Access being a database, only accepts values that match the column type where the data is being put. Any data that doesn't fit generates and error.
The reason that you get the error message after the fact is because of the way AccuTerm works. It first transfers the file to a temporary tab delimited text file. After the physical transfer is complete, it runs a conversion routine that attempts to load the text file into the format of your choice. Having the transfer complete without errors doesn't guarantee that the conversion will work. AccuTerm does it's best to try and figure out what type of data it is but it doesn't always work correctly. |
|
|
|
|
jgold
Moderator Group
Moderator Joined: December 29 2003 Location: United States Status: Offline Points: 48 |
Post Options
Thanks(0)
Quote Reply
Posted: February 06 2008 at 7:23am |
That could very well be the problem. Thanks Bruce. |
|
|
|
|
Sueglo
Newbie
Joined: January 11 2007 Location: United States Status: Offline Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: February 06 2008 at 7:33am |
|
Thanks to both of you, I went back in and reviewed the dictionaries, I didn't have anything on line 4, but to be sure I did a replace space with null. It still gave me the same msg.
I have a problem with my odbc tables that is similar to what you are saying with Access rejecting types it thinks it shouldn't have, so I will have to comb through some data to see if that is the case.
One other question/thought - I run into a problem on occasion with spaces in the header names, or using an "S" code on line 1 of the dictionary, could that be a problem with the ftd transfer??
Thanks for the suggestions, if you have anything else, I am all ears!
Susan
|
|
|
Susan
|
|
|
|
|
bneylon
Senior Member
Joined: March 03 2004 Location: United States Status: Offline Points: 103 |
Post Options
Thanks(0)
Quote Reply
Posted: February 06 2008 at 7:38am |
|
It may not be in <4>. Depends on what you run UD, UV, real PICK, etc. The value mark in the header of the dictionary was a little trick that allowed a report column header to have multiple lines. Depending on the dictionary types it could be a problem with <3>.
Bruce |
|
|
|
|
Post Reply
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
ftd errmsg using Access mdb extension
Topic Options
bneylon wrote: