From: jim.giner@suny.edu
oopd - read it so long ago I forgot the original description.
But - I never use the "long" method and when I tried it using the short
method I got the same error as you. But by substituting the real paths, it
worked.
I specified a large range to accomodate the max file size I expect and then
I set the logical arg. to True. Why not try it that way?
"Toby Sleigh" wrote in message
news:nKadnYk6b7DWPTPUnZ2dnUVZ8oOWnZ2d@bt.com...
>
> "Jim Giner" wrote in message
> news:49ae94e1$1@pnews.thedbcommunity.com...
>> As soon as I tried it out myself I remembered the problem.
>>
>> Because EXCEL is processing the command first (on an export, I guess pdox
>> processes the command first), you CANNOT use an alias in the paths of the
>> file references in the command line - you must be explicit. Works great
>> after you change those.
>>
>> Instead of
>> importspreadsheet(":myalias:myfile.xls",":myalias:myfile.db",........)
>> you must say
>> importspreadsheet("c:\\folder1\\subfolder1\\myfile.xls","c:\\
older1\\subfolder1\\myfile.db",.....)
>>
>> One of those un-documented quirks.
>
> ummmm..
> see my original post...............
>
> var
> dt DataTransfer
> endvar
>
> dt.setSource("C:\\SSin\\Feb09.xls")
> dt.setDest ("C:\\SSin\\Feb09.db")
> dt.setDestFieldNamesFromFirst(True)
> dt.setProblems ( True )
> dt.getSourceRange()
> dt.transferData ( )
>
> nor does
> importSpreadSheet("C:\\SSin\\Feb09.xls","C:\\SSin\\Feb09.db", "A1",
> "L300", false)
> work.
>
> thanks anyway.
>
>
>
>> "Toby Sleigh" wrote in message
>> news:VtadnX417ZtfGjPUnZ2dnUVZ8v-WnZ2d@bt.com...
>>>
>>> "Jim Giner" wrote in message
>>> news:49ae78aa$1@pnews.thedbcommunity.com...
>>>> Hate to repeat something, but the message you get indicates something
>>>> wrong when pdx attempts to identify how to format the fields. Now that
>>>> could be not recognizing the data, or simply not being able to name the
>>>> field (altho I thought it would default to something generic). YOu
>>>> never responded to Liz's question on field names.
>>>
>>> I did too, the field names came from the original Paradox table.
>>>
>>> Could you list them here?
>>>
>>> ok -
>>>
>>> Job Number
>>> Part Num
>>> Model
>>> QTY
>>> Price
>>> Availability
>>> Date Ord
>>> Ord by
>>> Description
>>> Our Ref
>>> Bonded
>>> ESCODid
>>>
>>>
>>>>>>
>>>>>> 2. Are you sure the column headers in Excel are valid Paradox field
>>>>>> names?
>>>
>>> Just in case I have tried renaming the column names to a,b,,,,,m , no
>>> difference.
>>> Then I deleted every column apart from the first column., no difference.
>>>
>>>> Once we see valid names are being used, the next ? would be - is the
>>>> data consistent across the board? I do believe that pdox may operate a
>>>> lot like excel and establish the "type" of each field by the contents
>>>> of the first row's cells. You may have to ensure that the first row in
>>>> your .xls contains representative data in each col so pdox has
>>>> something to work with from the start.
>>>
>>>
>>> The first row contains representative data. I've seen the problem you
>>> refer to before, when I've been importing manually, ie select then save
>>> as, when the column contained serial numbers and the first row or two
>>> was by chance a number, eg 1234567 then the next row was AB34567. The
>>> resultant table had the column as a number field, rather than alpha. (
>>> Or something like that , it was a while ago.)
>>>
>>>
>>> All I want to do is export a small table to Excel, email the new
>>> spreadsheet to a supplier, he fills in a couple of fields and sends the
>>> spreadsheet back to us.
>>>
>>
>>
>
>
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
