By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,122 Members | 927 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,122 IT Pros & Developers. It's quick & easy.

Problem Tables

P: n/a
I recall in my Paradox days that when appending records to a table or
updating records and data type conflicts or key violations were
automatically placed in tables called "Problem" or "Key_Viol". This was
very helpful in that Paradox performed the requested action while making a
table showing those records which were not included in the requested action
due to some type of conflict. The "Problems" or "Key Violators" could be
seen, analyzed and fixed just by viewing the table. I've been around
MSAccess (A97-XP) for a few years now and haven't seen anything comparable
to this great Paradox feature. When presented with a conflict, MSAccess
provides a 'Warning' that it did not add 'this many records for this reason
and did not add that many records for that reason and so on and so on', but
will not display the affected records. Similarly, Paradox had a "Subtract"
records function which would place the 'Subtracted' records in their own
'Subtracted' table. The closest thing to this that I've seen in Access is
the "Delete" query which does not automatically produce a table of the
subtracted (Deleted) records. Does anyone here know if MSAccess has a
similar feature or some "wizard" that will produce the same result in either
case?

TIA...
Earl Anderson
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
AFAIK, Access does not mimic the useful features you describe in Paradox.
The closest I know of it coming is the "Import_Errors" table it will produce
when some rows of an imported table fail.

You can "roll your own" routines to produce such tables by determining the
conditions and querying for them.
For example, if you want to append the records in TableA to those in TableB,
both with primary key PK, you could create a Select statement like this:
"SELECT * FROM TableA WHERE TableA.PK IN (SELECT PK FROM TableB)"
This will return all records from Table A which already have matches in
TableB.

HTH
- Turtle
"Earl Anderson" <is*****@rcn.com> wrote in message
news:bj**********@bob.news.rcn.net...
I recall in my Paradox days that when appending records to a table or
updating records and data type conflicts or key violations were
automatically placed in tables called "Problem" or "Key_Viol". This was
very helpful in that Paradox performed the requested action while making a
table showing those records which were not included in the requested action due to some type of conflict. The "Problems" or "Key Violators" could be
seen, analyzed and fixed just by viewing the table. I've been around
MSAccess (A97-XP) for a few years now and haven't seen anything comparable
to this great Paradox feature. When presented with a conflict, MSAccess
provides a 'Warning' that it did not add 'this many records for this reason and did not add that many records for that reason and so on and so on', but will not display the affected records. Similarly, Paradox had a "Subtract"
records function which would place the 'Subtracted' records in their own
'Subtracted' table. The closest thing to this that I've seen in Access is
the "Delete" query which does not automatically produce a table of the
subtracted (Deleted) records. Does anyone here know if MSAccess has a
similar feature or some "wizard" that will produce the same result in either case?

TIA...
Earl Anderson

Nov 12 '05 #2

P: n/a
"Earl Anderson" <is*****@rcn.com> wrote in message news:<bj**********@bob.news.rcn.net>...
I recall in my Paradox days that when appending records to a table or
updating records and data type conflicts or key violations were
automatically placed in tables called "Problem" or "Key_Viol". This was
very helpful in that Paradox performed the requested action while making a
table showing those records which were not included in the requested action
due to some type of conflict. The "Problems" or "Key Violators" could be
seen, analyzed and fixed just by viewing the table. I've been around
MSAccess (A97-XP) for a few years now and haven't seen anything comparable
to this great Paradox feature. When presented with a conflict, MSAccess
provides a 'Warning' that it did not add 'this many records for this reason
and did not add that many records for that reason and so on and so on', but
will not display the affected records. Similarly, Paradox had a "Subtract"
records function which would place the 'Subtracted' records in their own
'Subtracted' table. The closest thing to this that I've seen in Access is
the "Delete" query which does not automatically produce a table of the
subtracted (Deleted) records. Does anyone here know if MSAccess has a
similar feature or some "wizard" that will produce the same result in either
case?

TIA...
Earl Anderson

Ms-Access does display the affected records in a table called Paste
Errors. It is an automatic function and usually is preceded by an
Error message. However, anything that you delete is gone, unless you
specifically write a script to save it elsewhere first.
pjac
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.