I've got a report for which the user can supply free-form
comments.

Comments tb saved for the next time the report is run.

Comments can be Added/Changed/Deleted.

To me, that's a hidden table "zstblReportComment".

But how to key it to different (in the events that other reports
crop up with the same requirement) reports?

I guess Report.Name is the fallback position - and I guess the
likelihood of somebody renaming a report later is low....

But I'd really rather have something like a ReportID that is
unique to/embedded in the report.

I there anything "under the table" yet not *too* arcane that I
could use?
--
PeteCresswell

If you don't mind using the undocumented MSysObjects table, the ID field
appears to be constant.

You might want to read MichKa's comments about the advisability of basing
things on the system tables
http://www.trigeminal.com/usenet/usenet017.asp

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele
Co-author: Access 2010 Solutions, published by Wiley
(no e-mails, please!)

"(PeteCresswell)" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I've got a report for which the user can supply free-form
> comments.
>
> Comments tb saved for the next time the report is run.
>
> Comments can be Added/Changed/Deleted.
>
> To me, that's a hidden table "zstblReportComment".
>
> But how to key it to different (in the events that other reports
> crop up with the same requirement) reports?
>
> I guess Report.Name is the fallback position - and I guess the
> likelihood of somebody renaming a report later is low....
>
> But I'd really rather have something like a ReportID that is
> unique to/embedded in the report.
>
> I there anything "under the table" yet not *too* arcane that I
> could use?
> --
> PeteCresswell

I store all my reports in a eReport table.. and I assign it a
eReportID. When someone brings me a report, I have to look it up in
the table (before I can work on it).

I just don't think that basing anything on the actual report name is
advisable.. because it's prone to change over time (and you don't want
to have to rename your database objects)

I store the reportName and the reportTitle and the reportFooter in a
single table.. and it's easy to update those in one place.

Thanks

-Aaron



On Jul 21, 10:41*am, "(PeteCresswell)" <x...@y.Invalid> wrote:
> I've got a report for which the user can supply free-form
> comments.
>
> Comments tb saved for the next time the report is run.
>
> Comments can be Added/Changed/Deleted.
>
> To me, that's a hidden table "zstblReportComment".
>
> But how to key it to different (in the events that other reports
> crop up with the same requirement) reports?
>
> I guess Report.Name is the fallback position - and I guess the
> likelihood of somebody renaming a report later is low....
>
> But I'd really rather have something like a ReportID that is
> unique to/embedded in the report.
>
> I there anything "under the table" yet not *too* arcane that I
> could use?
> --
> PeteCresswell

Per a a r o n . k e m p f @ g m a i l . c o m:
>I just don't think that basing anything on the actual report name is
>advisable.. because it's prone to change over time (and you don't want
>to have to rename your database objects)

That was my feeling too.

What I went with was the ID number in the MSysObjects table.

That way somebody later on could (about a .001 percent
chance...but still...) change the name of the report and not
break my little scheme.
--
PeteCresswell