RE: dbexport Error 452, loc_open() failed

What version are you on, I am not sure, but I seem to recall a bug in dbexport which was something like this in 7.30 or something This is only one of those vague recollections though... Will >===== Original Message From Rudy Fernandes <rferdy@americasm01.nt.com> ===== >It is possible that a table, with a text column, has a missing blob. You >should get the same error if you attempt to unload that table. > >Possible solution: > >Identify the row(s) on which you have the problem by narrowing your >unload statement. Call in the UN and go meet your users. Set the text >column to null. When you can unload the full table, retry your dbexport. > >Rudy > >Andy Hall wrote: > >> When I do a dbexport of our online database it >> stops on the same table every time with this error, >> error -452 loc_open() failed. >> I looked up the error, but doesn't really mean anything for this. >> >> I can add and delete records, print them all out >> using odbc, no problem. >> >> I tried using unload in db-access, when I hit run it >> does nothing, weird, works fine on other tables. >> >> I could use dbexport before, don't know what happened. >> >> What could be the problem? >> >> If table is corrupt? how would I fix? >> >> Thanks, Andy. ------------------------------------------------------------ This e-mail has been sent to you courtesy of OperaMail, as a free service from Opera Software, makers of the award-winning Web Browser, Opera. Visit us at http://www.opera.com/ or our portal at: http://www.myopera.com/ Your free e-mail account is waiting at: http://www.operamail.com/ ------------------------------------------------------------