Article View: borland.public.cppbuilder.database.ado
Article #2060Interesting new problem
From: Ted Byers
Date: Thu, 27 Nov 2003 20:30
Date: Thu, 27 Nov 2003 20:30
17 lines
1689 bytes
1689 bytes
I will have two database files. In one, which is to be read only, there is a lookup table that must be used in the second. The second must not allow values that are not found in this lookup table in the first. How can this be done? Is this a constraint I can embed directly into the database files, or do I have to ensure it in my code? 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. FTR, I am using BCB5, and connecting to the databases entirely using ADO/ADOX in code. Thanks, Ted
Technical Details
Message-ID:
<3fc65fc9@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10698b,b014de63272f8cbe,start X-Google-Attributes: gid10698b,public X-Google-ArrivalTime: 2003-11-27 12:40:56 PST From: "Ted Byers" <r.ted.byers@sympatico.ca> Newsgroups: borland.public.cppbuilder.database.ado Subject: Interesting new problem Date: Thu, 27 Nov 2003 15:30:38 -0500 Lines: 19 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 NNTP-Posting-Host: 65.95.124.67 Message-ID: <3fc65fc9@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1069965257 65.95.124.67 (27 Nov 2003 12:34:17 -0700) Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail