Hi, Gary Providing you have removed all the places where the General field was used, I don't believe you have to do anything more except remove the field from the .DBFs. The forms, reports, etc. do not store any information about the table structures, only about the fields they are referencing.
Suggestion: Extract a 1-record test file, delete the General field, and try running with that to catch any leftovers. Dan On 01/31/12 11:40, Gary Jeurink wrote: > The saga of a rookie fixing early mistakes continues. With this forum's > advice, I no longer put photo's into a general field. I added one integer > field that stores a file-No that will locate the picture. The extra field > allows multiple records to share a photo in appropriate cases. Now I am > ready to delete the field that contained the photos. This will make a huge > difference on the size of this table. > > > > I have edited all views or connected tables to no longer use this field but > am I still looking at rebuilding every form that uses this table just > because the table record field list will change? Even if so, it will be > worth it as the storing pictures in general fields was unreliable as they > would occasionally swap photos with other records. > > Gary Jeurink _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
