i am posing this generically, with hopes that someone can provide some
insight to my specific problem.

generically what i would like to do is to have many layouts (with
different, sometimes similar, underlying tables) Each of the layouts
would have underlying tables that contain a global that ID's the
layout.

I would then like to create a script that would look up the global's
value and display a custom dialog with the looked up information from a
related table such as 'TblHelp' where 'TblHelp' is related to
underlying table 'TblData' on a global field of 'TblData' to a serial
field in 'TblHelp'.

Hopefully this question might make some sense?

thanks much,
sg

OS=MS

Ver=7 Developer

Host=Server 7 Advanced

For what I understand - and I may be wrong - I think you could create a
special one record table, with regular - ie accessible to any table via
relationships - fields, where to put what I call 'semi-permanent' data such
as owner name, value lists, etc.
Would this work for you ?
Remi-Noel

"MaximalVariance" <StephenTGallagher (AT) gmail (DOT) com> a écrit dans le message de
news: 1164746246.337726.315970 (AT) 80g200...oglegroups.com...

Remi-Noel Menegaux wrote:
hmmm...thank you remi, that is an interesting idea. i suppose i could
define an un-editable field on my layout and relate to a sepereat
table. the un-editable field could be defined via a portal as a text
box with a scroll bar and display the relevant message, tied to the
global of the underlying table that is set according to what message i
wish to display. not what i had in mind, but intriguing.

thanks for the insight and time.

best,
sg

Just some small comments : in that one record table (say called 'Param') you
may have one regular (not global) text field in which you put your messages
separated by a 'CR' (carriage return or paragraph return), and then on any
other table layout, you don't need a portal, just a value list taking its
contents to that field with a 1 to 1 (constant = 1) relationship with the
'Param' table.
I use this method - like many people do - almost systematically in each of
my solutions.
The advantage is that you have 'pre-cooked' lists, that are still modifiable
by the DB admin user (maybe with a password), when he needs and/or wants it.
E.g. in Europe the 'VAT' percentages that are sometimes changed by the
government, or more simply the 'Company' to whom you sold your solution
(this is not a list but just a plain single line text, unless you add a
'Sites' list for that client) for which you may put its name, address, logo,
etc. and show the 'logo' for example on the top left of each of your
layouts. I use it for almost all value lists, as the client wants always to
adjust their contents (for example the list of the 'Banks' he is dealing
with ) and he can do that by himself without bothering you. I also use that
to list various passwords types (owner, cashiers) all in an 'invisible'
layout only accessible from a 'keys box' button calling a script in which I
imbed a hard 'OK' password that then shows the passwords layout. These are
just (my) examples.
Remi-Noel

----------------Original message-------------
Remi-Noel Menegaux wrote:
hmmm...thank you remi, that is an interesting idea. i suppose i could
define an un-editable field on my layout and relate to a sepereat
table. the un-editable field could be defined via a portal as a text
box with a scroll bar and display the relevant message, tied to the
global of the underlying table that is set according to what message i
wish to display. not what i had in mind, but intriguing.

thanks for the insight and time.

best,
sg