![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
inspecting the text file, I find nothing wrong with the line that I can see. Here's an example: |
#3
| |||
| |||
|
|
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? |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
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? |
#6
| |||
| |||
|
|
There aren't many alerts like this, but still, it's annoying. What's the reason? |
#7
| |||
| |||
|
|
"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.. |
#8
| |||
| |||
|
|
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? |
#9
| |||
| |||
|
|
"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) |
#10
| |||
| |||
|
|
I don't think I've ever heard of opening a text file in a text editor before. |
![]() |
| Thread Tools | |
| Display Modes | |
| |