G
Guest
I have an Access DB linked to an Excel file that is automatically updated
nightly. In one of the columns in Excel (which should always be a number),
if there is no data for that particular line, there will be a blank cell,
rather than a value of "0". The formatting for all the cells in the Excel
file is "General".
The Acess DB sits on a network drive and can be accessed by several users in
the course of the day. I have recently come across a situation where the
first 15-20 rows of data have no data (blank cells) in one of the columns,
and different users will get different results when they update that linked
table. For example, when I update the links and resulting queries, Access
recognizes that column of data as a number field and everything works as
designed, but when another user on another PC updates links and queries,
Access recognized that same column as text, and everything bombs out.
The base excel file is systematically generated, and I am not the owner of
the file (and therefore cannot make changes to the excel file).
Is there a way of ensuring that Access will recognize this column as a
number field, regardless of which user is updating the DB, without modifying
the Excel file?
nightly. In one of the columns in Excel (which should always be a number),
if there is no data for that particular line, there will be a blank cell,
rather than a value of "0". The formatting for all the cells in the Excel
file is "General".
The Acess DB sits on a network drive and can be accessed by several users in
the course of the day. I have recently come across a situation where the
first 15-20 rows of data have no data (blank cells) in one of the columns,
and different users will get different results when they update that linked
table. For example, when I update the links and resulting queries, Access
recognizes that column of data as a number field and everything works as
designed, but when another user on another PC updates links and queries,
Access recognized that same column as text, and everything bombs out.
The base excel file is systematically generated, and I am not the owner of
the file (and therefore cannot make changes to the excel file).
Is there a way of ensuring that Access will recognize this column as a
number field, regardless of which user is updating the DB, without modifying
the Excel file?