Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 9,633 of 9,834    |
|    Jim Giner to YOu never    |
|    Re: Import from Excel .xls problem    |
|    04 Mar 09 07:48:41    |
      From: jim.giner@suny.edu              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. Could you list them here?       >>       >> 2. Are you sure the column headers in Excel are valid Paradox field       >> names?       >>              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.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca