K
Ken Paul
I need to know the details of why an ODBC driver displays
a version of "not marked" in the ODBC Data Sources
Administrator. I'm trying to deploy an ODBC driver to
multiple machines, and on some machines the driver lists
as "not marked" and is not usable. I've checked registry
entries and file attributes, and the only difference I
can see is that in most (but not all) of the failed cases
the driver's dll shows a create date that is different
than the last modified date. However, changing the
create date in these cases does not fix the problem. Can
someone tell me the exact tests performed in determining
this "not marked" condition?
a version of "not marked" in the ODBC Data Sources
Administrator. I'm trying to deploy an ODBC driver to
multiple machines, and on some machines the driver lists
as "not marked" and is not usable. I've checked registry
entries and file attributes, and the only difference I
can see is that in most (but not all) of the failed cases
the driver's dll shows a create date that is different
than the last modified date. However, changing the
create date in these cases does not fix the problem. Can
someone tell me the exact tests performed in determining
this "not marked" condition?