Mark A Matte
markamatte at hotmail.com
Wed Feb 11 12:19:32 CST 2009
The data is in an Informix database. I only have a link to the table. If I had this exported to text by the DBA...I could easily deal with it...even as a 2 gig text file. The problem was anytime I would reference the table/field in a query or vba...access would crash when it reached this record...I was looking for a way to determine a bad record, skip it...and keep going. I used a slightly manual process to isolate the bad records. This instance has been resolved...but by a manual process. Original question was still how to avoid the crash. Thanks, Mark A. Matte ---------------------------------------- > Date: Wed, 11 Feb 2009 09:06:50 -0800 > From: davidmcafee at gmail.com > To: accessd at databaseadvisors.com > Subject: Re: [AccessD] Import Bad data? > > Can you export the file to a CSV and open it in Notepad? > > By looking at the record(s) do you know what character is causing the > problem? If so can you simply do a find & replace in Notepad to change > the character to some other character? > > David > > On Wed, Feb 11, 2009 at 5:55 AM, Susan Harkins wrote: >> I'd run it through Excel first -- import it, save it -- import it into >> Access via the Excel worksheet. Might not work, but I've seen it work. >> >> Susan H. >> ----- Original Message ----- >> From: "Mark A Matte" >> To: >> Sent: Monday, February 09, 2009 11:05 AM >> Subject: [AccessD] Import Bad data? >> >> >> >> Hello All, >> >> I'm not expecting an answer I'll like...but I'll try. >> >> I'm importing a large number of records from Informix to Access via odbc. >> There is a large text/memo field...that apparently has some characters >> access does not like. I do not get an error message...access just says "an >> error has occurred...do you want to tell MS"...then closes. >> >> I'm trying to think of a way to detect/program around this. So far...its a >> very manual process. I loop through 2 days worth at a time...that way I >> don't have to start over from the beginning everytime. When it crashes...I >> pull in just the PKs for that date range...loop through them...imort the >> text field 1 record at a time...store in temp table...when it crashes...I >> compare the PKs to the temp table...the next PK not in the temp is the >> offender. >> >> This is very manual and time consuming...any ideas/suggestions? >> >> Thanks, >> >> Mark A. Matte >> >> >> _________________________________________________________________ >> Windows Live™: E-mail. Chat. Share. Get more ways to connect. >> http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_AE_Faster_022009 >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com >> >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com >> > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com _________________________________________________________________ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_022009