K
kev100 via AccessMonster.com
I'm using Access 2002 to Link to an Visual FoxPro 7.0 .dbf table via ODBC.
In some situations it is Imported rather than Linked.
The entire table is also sometimes copied to another drive (in an attempt to
simply isolate it from the original).
The .dbf table itself is used by a predictive dialer application which can be
pretty sensitive. Often, when the Access application is Linking, Importing,
or copying it, that Predicitive Dialer program is actively using it (reading
/ writing).
Not always.....but a few times, that Dialer application has simply locked
soon after its table is being accessed by the Access 2002 program. I'm
suspecting that doing so somehow alters / disturbs that .dbf table, even
though nothing is being edited , written , deleted, etc.
I'm not familiar with exactly what occurs to a .dbf when it is
linked/imported via ODBC. Does some minor alteration occur or are these
problems simply a timing coincidence?
Thanks
In some situations it is Imported rather than Linked.
The entire table is also sometimes copied to another drive (in an attempt to
simply isolate it from the original).
The .dbf table itself is used by a predictive dialer application which can be
pretty sensitive. Often, when the Access application is Linking, Importing,
or copying it, that Predicitive Dialer program is actively using it (reading
/ writing).
Not always.....but a few times, that Dialer application has simply locked
soon after its table is being accessed by the Access 2002 program. I'm
suspecting that doing so somehow alters / disturbs that .dbf table, even
though nothing is being edited , written , deleted, etc.
I'm not familiar with exactly what occurs to a .dbf when it is
linked/imported via ODBC. Does some minor alteration occur or are these
problems simply a timing coincidence?
Thanks