S
SimpleSync
Karl --- tried to reply but the message is refused for some reason ??
Each Excel file has just one row:
Last,First,Initials,Phone,Fax,Street,City,State,Country,Company,Department,etc......
I want to import each of these files into a separate Table in an Access DB.
Once this is done each table is empty, but has column headers in place...in
effect the tables are 'primed'.
Our software package then takes an incoming LDIF file from Active Directory
and does an ODBC update, matching the AD attribute labels with the column
headers in Access.
When I look in the design View, all of the fields in the Access table
default to settings of:
Required: No
Allow Zero Length: No
Indexed: No
Since none are required I would have expected to be able to be able to
handle missing values in some fields from AD, but when I run the update it
fails. Example: In AD the 'Assistant' fields are normally blank and cause
the following error:
[Microsoft][ODBC Microsoft Access Driver] Field 'SQL2.Assistant' cannot be a
zero-length string. (SQL-HY000)(DBD: st_execute/SQLExecute err=-1)
SQL2 is my table. Assistant is a column header. Most AD records do not have
any value in this field.
I can import each Excel file into an Access table, and then manually change
the setting to: Allow Zero Length: Yes
This works fine, but for testing we may need to build multiple tables, with
as many as 80 columns - and I would really like to avoid having to change
this value for all 80 fields.
Thanks,
Jerry
Each Excel file has just one row:
Last,First,Initials,Phone,Fax,Street,City,State,Country,Company,Department,etc......
I want to import each of these files into a separate Table in an Access DB.
Once this is done each table is empty, but has column headers in place...in
effect the tables are 'primed'.
Our software package then takes an incoming LDIF file from Active Directory
and does an ODBC update, matching the AD attribute labels with the column
headers in Access.
When I look in the design View, all of the fields in the Access table
default to settings of:
Required: No
Allow Zero Length: No
Indexed: No
Since none are required I would have expected to be able to be able to
handle missing values in some fields from AD, but when I run the update it
fails. Example: In AD the 'Assistant' fields are normally blank and cause
the following error:
[Microsoft][ODBC Microsoft Access Driver] Field 'SQL2.Assistant' cannot be a
zero-length string. (SQL-HY000)(DBD: st_execute/SQLExecute err=-1)
SQL2 is my table. Assistant is a column header. Most AD records do not have
any value in this field.
I can import each Excel file into an Access table, and then manually change
the setting to: Allow Zero Length: Yes
This works fine, but for testing we may need to build multiple tables, with
as many as 80 columns - and I would really like to avoid having to change
this value for all 80 fields.
Thanks,
Jerry