Re: What's wrong with this trigger

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

You are right, on many occasions (or designs), audit tables doesn't require
their own identiy field.

For your question about queries, SP returns RowSets and not tables or views,
so you cannot use them directly inside a Select query but you can convert
them back to tables by using the instruction OpenRowSet, OPENDATASOURCE et
OPENQUERY.

However, easier solutions would be to use User Defined Functions (UDF)
returning table variables or to use subqueries. The level and complexity of
subqueries that you can write with T-SQL is much greater than with Access.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC


"Jeff via AccessMonster.com" <forum@xxxxxxxxxxxxxxxxx> wrote in message
news:c165c17ef0324795b431f1467f8ab0fe@xxxxxxxxxxxxxxxxxxxx
> After reviewing what the previous datbase developer did with the audit
> tables I realized that there was no need for an identity field in the
> audit
> tables. Eveything works fine now that I removed the identity fields.
>
> I'm still learning all this on the fly as most of my experience is with
> Access on it's own.
>
> On a seperate topic, one thing in Access which was possible was to build a
> query based on other queries. Is this possible with stored procedures
> without creating Temp tables?
>
> --
> Message posted via http://www.accessmonster.com


.