Lew: Perhaps some suggestions at:
http://www.techrepublic.com/article/10-tricks-for-handling-null-values-in-microsoft-access/6125114 On Tue, Sep 6, 2011 at 6:29 PM, Lew Schwartz <lew1...@gmail.com> wrote: > I generate some dbf's and xml's for one of my endusers to import. > Unfortunately, this is an MS Access (only) user and blank/empty > strings are universally imported as Access nulls (by which I think she > means 0 length strings). Blankness is handled differently in a lot of database and application languages. FoxPro is as quirky as they get with fields like logical ("Boolean" or binary) having states of True, False, NULL and ISBLANK(). That's not binary, that's quaternary. In the past, I've handled these situations by creating a "special" export for otherwise-enabled users. You could do a SQL Select of the result you're exporting and specify (IIF(EMPTY(myfield),"BLANK", myfield)) to fill the fields with a value otherwise not found in the application. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: ProFox@leafe.com 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/cacw6n4uqhrf8-trpenjk1aps2rwe_hn_g3gck6fzatuxula...@mail.gmail.com ** 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.
