Are you talking about storing text for a database application which will be
used in multiple languages?
We did something similar to this a couple of years ago for an application we
had written for one government client. When we demonstrated it for another
govt client, they didn't like the captions (wanted their own verbiage). So
we created a table (I'll call it tbl_Form_Captions) that contained fields
(FormName, Version, TextID, and TextString), and created a Version field in
our application parameters table (tbl_AppParameters).
In the forms Load event, we called a subroutine that looped through each of
the controls on the form and checked if its Tag property had a numeric
(TextID) value associated with it. If it did, we set the Caption property to
the TextString value from tbl_Form_Captions that corresponded to the Forms
name, application Version, and the TextID value). This may take the form a
little longer to load, but if you construct your subroutine properly, it will
be negligible. We put tbl_Form_Captions in the applications front end to
help speed it up.
The only real challenge was filling in the TextString values for the various
versions of the application.
HTH
Dale
--
Don''t forget to rate the post if it was helpful!
email address is invalid
Please reply to newsgroup only.
