🚀 go-pugleaf

"Dwayne" <myfrienddr@yahoo.com> wrote in message
news:3fcfb8ea@newsgroups.borland.com...
>         Hello Ted,
>
> Ted >> If the latter, how can I protect
> against the possibility that the user uses MS Access to change the data so
> as to violate, however inadvertently, this constraint?  Right now, I am
> relying on the fact that my program does not add any value to the second
> that isn't in the first, but this strikes me as a little risky, given the
> possibility of curious eyes getting into the DB using MS Access.<<
>
>         Open the Dbase as exclusive access only. I believe this will solve
> your problem.
> I have not checked it out yet to confirm,  But give it a try.
>
>
Hi  Dwayne

Thanks

I aleady do.  The problem isn't when my program is running.  The problem is
when it isn't.  The database files are just mdb files, MS Access's native
format, and if the user has Access installed, there is nothing to prevent
him from using Access to open the database and play with the data.  In fact,
there is a trivial cosmetic error in two records in the USDA database which
is easiest to fix by opening the file in Access, finding the relevant
records in the relevant table, and correcting the error. If theuser has the
ability to do this, he also has the ability to open the other database files
and mess witht he data without the safeguards built into my code.  What I'd
like to be able to do is submit an SQL statement to one of the database
files in order to establish a relationship between a field in a table in
that file and a field in a table in another file, so that if the user knows
enough to be able to open and edit tables using Access, he'd have to
deliberately break that connection before he could mess up the required
relationships (so, when the user opens these files in Access, Access would
open both by default and check the relational integrity of any edit he
makes, unless he knows enough about Access to break that relationship).

Cheers,

Ted