dbTalk Databases Forums  

Mildly annoying import glitch

comp.databases.paradox comp.databases.paradox


Discuss Mildly annoying import glitch in the comp.databases.paradox forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Doug Kanter
 
Posts: n/a

Default Mildly annoying import glitch - 02-22-2006 , 10:04 AM






Using PdoxDOS 4.5, importing a comma delimited file. During the initial scan
of the file, Pdox reports "Invalid format in record <whatever>". Upon
inspecting the text file, I find nothing wrong with the line that I can see.
Here's an example:

119 ,934635,70652-00267,00267,ARROW PLASTICS SIP-A-TRAINER ,1,7
OZ,0,0,3.500,1.090,0

There aren't many alerts like this, but still, it's annoying. What's the
reason?



Reply With Quote
  #2  
Old   
Tony McGuire
 
Posts: n/a

Default Re: Mildly annoying import glitch - 02-22-2006 , 10:10 AM







Quote:
inspecting the text file, I find nothing wrong with the line that I can see.
Here's an example:

What are the formats for those fields?

--

Tony McGuire
"It's not about having enough time. It's about priorities."
___________________________



Reply With Quote
  #3  
Old   
Doug Kanter
 
Posts: n/a

Default Re: Mildly annoying import glitch - 02-22-2006 , 10:18 AM



"Tony McGuire" <png.paradoxcommunity@com> wrote

Quote:
inspecting the text file, I find nothing wrong with the line that I can
see.
Here's an example:


What are the formats for those fields?
119 - Division number - treated as A3
934635 - Item Code - treated as A6
70652-00267 - UPC - treated as A11
00267 - Case UPC Code - treated as A5
ARROW PLASTICS SIP-A-TRAINER - Description - treated as A30 (some longer
than the one shown here)
1 - Pack (per case) - Short number (S)
7 OZ - Size - treated as A6
0 - Case Height - treated as S
0 - Case Width - treated as S
3.500 - Weight - treated as N
1.090 - Cube - treated as N

When I say "treated as", I mean it's how I intend for restructure after the
import is complete. Pdox obviously makes its own guesses during the import.




Reply With Quote
  #4  
Old   
Tony McGuire
 
Posts: n/a

Default Re: Mildly annoying import glitch - 02-22-2006 , 10:23 AM




I forget. Does PdoxDOS have the ability to import into an existing table?

If so, why not import into your own table then add into the actual table?

You'd be able to stop some of the 'glitches' of allowing Paradox total control,
and get a 'problems' table with (possibly) better descriptions of the issues.


Of course, this assumes pdoxDOS imports into existing table.



--

Tony McGuire
"It's not about having enough time. It's about priorities."
___________________________


Reply With Quote
  #5  
Old   
Doug Kanter
 
Posts: n/a

Default Re: Mildly annoying import glitch - 02-22-2006 , 10:32 AM



"Tony McGuire" <png.paradoxcommunity@com> wrote

Quote:
I forget. Does PdoxDOS have the ability to import into an existing table?
Yes, it does. There's an "Append" option.


Quote:
If so, why not import into your own table then add into the actual table?
Actually, this is the purpose of the initial table. Within this file is data
for several different divisions of the same company. The next step would be
to query that table based on the first field (division number), and use a
ready-made insert query script to insert the Answer table into an array of
individual tables.

Maybe I should simply create the initial table manually, and see if the
Append option will force Pdox to keep quiet.




Reply With Quote
  #6  
Old   
Steven Green
 
Posts: n/a

Default Re: Mildly annoying import glitch - 02-22-2006 , 11:02 AM




"Doug Kanter" <ancientangler (AT) hotmail (DOT) com> wrote in message
Quote:
There aren't many alerts like this, but still, it's annoying. What's the
reason?
since the import file doesn't have quoted strings, and much of that stuff is
made up of numbers, it's easy to see why there's a problem.. my guess is
this field:

70652-00267

but there's no way for me to know for sure, without doing it myself.. not
that I have any desire to do so (g)..

FWIW, if I had to import stuff like that, with questionable content, I'd
open an editor session, scan it, and slam the results into a table myself..
that way, I can do a ton of formatting and analysis that a straight import
can't..

--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales - Corel CTech Paradox

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards




Reply With Quote
  #7  
Old   
Doug Kanter
 
Posts: n/a

Default Re: Mildly annoying import glitch - 02-22-2006 , 11:16 AM



"Steven Green" <greens (AT) diamondsg (DOT) com> wrote

Quote:
"Doug Kanter" <ancientangler (AT) hotmail (DOT) com> wrote in message

There aren't many alerts like this, but still, it's annoying. What's the
reason?

since the import file doesn't have quoted strings, and much of that stuff
is made up of numbers, it's easy to see why there's a problem.. my guess
is this field:

70652-00267

but there's no way for me to know for sure, without doing it myself.. not
that I have any desire to do so (g)..

FWIW, if I had to import stuff like that, with questionable content, I'd
open an editor session, scan it, and slam the results into a table
myself.. that way, I can do a ton of formatting and analysis that a
straight import can't..
What do you mean by "editor session", Steve? And, if that UPC field was a
problem, why does Pdox wait until line 20,000-something in the file to have
a problem?




Reply With Quote
  #8  
Old   
Steven Green
 
Posts: n/a

Default Re: Mildly annoying import glitch - 02-22-2006 , 12:16 PM



"Doug Kanter" <ancientangler (AT) hotmail (DOT) com> wrote in message
Quote:
What do you mean by "editor session", Steve?
{Editor}{Open} for starters, then manipulate the content.. there's a brave
new world out there, waiting to be explored (g)


Quote:
And, if that UPC field was a problem, why does Pdox wait until line
20,000-something in the file to have a problem?
like I said.. a) it was a guess.. b) I don't have the file.. and c) there
are other/better ways to import..


--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales - Corel CTech Paradox

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards




Reply With Quote
  #9  
Old   
Doug Kanter
 
Posts: n/a

Default Re: Mildly annoying import glitch - 02-22-2006 , 01:27 PM



"Steven Green" <greens (AT) diamondsg (DOT) com> wrote

Quote:
"Doug Kanter" <ancientangler (AT) hotmail (DOT) com> wrote in message

What do you mean by "editor session", Steve?

{Editor}{Open} for starters, then manipulate the content.. there's a brave
new world out there, waiting to be explored (g)
Thanks, Steve. I don't think I've ever heard of opening a text file in a
text editor before. This is an amazing concept.




Reply With Quote
  #10  
Old   
Steven Green
 
Posts: n/a

Default Re: Mildly annoying import glitch - 02-22-2006 , 02:01 PM




"Doug Kanter" <ancientangler (AT) hotmail (DOT) com> wrote in message
Quote:
I don't think I've ever heard of opening a text file in a text editor
before.
I know what you really meant, therefore I have no problem saying THAT'S THE
DUMBEST THING I'VE EVER HEARD (vbg)


--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales - Corel CTech Paradox

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.