Wrong. "a form to document a database" is for my internal use in
deference to the next developer who will be supporting this db and who
was not involved in its design or evolution.
I'm documenting the "why" of certain forms, components, RUN SELECT code,
EEPS etc. and the _reasons _they do what they do - logic descriptions
that, I believe, are beyond the capabilities of rote db documenters.
Your second paragraph was helpful.
Doug
On 8/28/2020 9:21 AM, A. Razzak Memon wrote:
So, if I understand your question correctly, you want users to muck
with the form and know all about the database, while running the form
in BROWSE, EDIT, OR ENTER mode. Right?
The Data Dictionary (F3) feature is only available in design mode and
not the run time.
To document your database, there are various swift techniques to
accomplish the goal, and not by giving users the access to full Data
Dictionary.
Hope it helps!
Razzak
At 10:08 AM 8/28/2020, Doug Hamilton wrote:
Forms 101 questions: How do I get F3 to bring up the Data Dictionary
when running a form?
I'm working on a form to document (gasp!) a database and use of the
F3 Data Dictionary in this form is critical.
X.5 E, 8/20/20 release.
Doug
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/55f0a3d4-c2c9-4a28-5d17-2b3bfddb40a7%40wi.rr.com.
