RE: GLH records uploading problem -- BPCS-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Victor,

You will encounter this problem when trying to append records with a null value (as opposed to a Blank or Zero-Length String) in one or more fields in the records. The table on the 400 is defined to not allow NULLs. To get around this change the table in Access to accomodate Zero-Length Strings and update the NULLs to Blanks, then upload.

In Access modify the definition the table you are uploading. Select the field(s) that contain Null values. Set the properties of those fields as follows:

Required = Yes

Allow Zero Length = Yes

Then open the table in Data View mode. Go to any fields in the records you are uploading that contain NULLS and press the space bar. This will enter a zero-length string instead of a NULL. The 400 will not choke on the blank the same way it chokes on the NULL. Alternatively you can write an update query and set <FieldName> = "" where <FieldName> is NULL.

Best wishes,

Geo

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.