General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
MJ - there is one nasty -
if you are relying on ODBC connection for non-vfp access to that data -
and you have a table in a dbc -
and this table has a trigger - oh lets say - for INSERT -
the trigger will not fire ...
For OLE DB - it will fire [most of the time] but then you have to get that 'good' VFP OLE-DB driver set [which you probably have already]
hth - mondo regards [Bill]
>Hey all,
>
>I posted a while back wondering why transactions weren't working on our tables...it was because they were free tables.
>
>If we add some of our formerly-free tables to a DBC so that we can use transactions on them, what are the downsides? I am worried because I can't think of any right now other than the fact that the tables will not be accessible in older Fox apps (which is OK, we are all VFP 7.0 now). Usually when I can't think of anything that just means I am forgetting something awful... *smile*
>
>As far as I know, the tables should still open the same, have all the same indices available, etc. Can anyone point out any problem we may have with tables being part of a DBC instead of being free? If there is no downside, we will be ready to start using transactions more effectively!
>
>Thanks,
>JoeK
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only