Search results

Hi all, So I did some detective work and found that there was likely to be some corrupted data after we imported a few thousand records into the DB and the record id numbers went into an autonumber field (the primary key field). Anyway, we remade the primary key field and now we are able to...

Thanks for all of the advice. I had been exporting from the backend in the short term but it sounds like I really need to work out what is going on that is preventing the front end from successfully running the export script so I'm going to try DBGuy's suggestion to isolate the problematic table...

Hi all, I managed to run the export successfully from the backend so I think DBGuy was right - there must have been some corruption in the front end. Is there any reason why I shouldn't just add a form with a button to the back end to run the 30-or so exports in one go from there from now on...

Hi DBGuy, Thanks for the warm welcome and for your suggestion. I've since realised that the error is also occurring when I run the export manually from the front end, but not the back end. In other words, when I run the export from the back end, It seems to parse all the records perfectly but...

Hi, I have set up a button linked to the "runsavedimportexport" function so that I can export my tables to CSV files in one click. This was working fine for a while but after I recently expanded the size of my database, I am now encountering export errors for one particular table. Oddly, I...