Search results

  1. L

    error when exporting to text format

    Thanks Dave, I'll keep that in mind. But why Access has this restriction? Does it keep the table in an array?
  2. L

    error when exporting to text format

    Today I spoke to an Access programmer from our another department. As a check, he imported all fields of my .csv as text and tried to export it to a .txt file. He got an error message regarding field number 129, and numbers in the message were 32767 and 32907~255*129! So it seems that you both...
  3. L

    error when exporting to text format

    Dave, I do not generate the input .csv myself, another department does that. My records are approximately 2000 symbols long, they include numbers and text strings enclosed in "" and separated by ; . I never tried a query for importing/exporting.
  4. L

    error when exporting to text format

    Dave, Thanks for useful thoughts. I do not have any memo fields, otherwise I would already suspect something....I also do not see anything strange in Notepad, besides some missings (which is normal for this type of data).
  5. L

    error when exporting to text format

    I did mention that the range of integer fields causing the problem was rather small, say, 1-1000. I was able to export the table when I deleted about 20 unused fields, so this is my solution of this problem at the moment.
  6. L

    error when exporting to text format

    So the string is never too long (as far as the output window goes). However, I still do not see the reason for the error message.... Regarding using VBA for exporting: we will certanly review the procedure, but this will take time. Doing it in VBA right now is too risky, considering the...
  7. L

    error when exporting to text format

    David, This was the output. I do not quite understand what does it mean, you do? 114289 1055 114290 667 114291 1035 114292 1043 114293 1032 114294 1165 114295 1033 114296 1035 114297 1083 114298 1043 114299 1052 114300 1043 114301 1043 114302 1078 114303 1072 114304 1055 114305 1048 114306...
  8. L

    error when exporting to text format

    Thanks for your advice, David. I find it hard to believe when I see the first lines of the input text file in Notepad. But I realise that I do not see the rest of the file, so probably it is worth to check out. Do you have any idea how to check the field size programmatically?
  9. L

    error when exporting to text format

    Unfortunately I cannot do that, I work with bank client data.
  10. L

    error when exporting to text format

    No, never. My text fields are rarely longer than 20 symbols. Once I got this error message about an integer field with client age (maximum 98 years). I was really surprised to see in the message numbers like 32999 etc. Obviously something else is going on....
  11. L

    error when exporting to text format

    Hi David, Thanks for your reply. I have no integer fields for which Long representation would be needed. The fields mentioned in error message mostly have a range like 1-1000, or are (half) empty. I also find it strange that they are all located at the right-hand end of the table, it looks like...
  12. L

    error when exporting to text format

    Hello, I need to export to .txt (delimited) an Access table containing 250 fields and 115000 records. I use the export wizard. Shortly after hitting 'finish' I get the following message: The field FIELD contains a start position of '32802'. The maximum start position allowed is 32767...
Back
Top Bottom