I know it ain't pretty, but it's built in - The 'Documenting Wizard' - but you'll need to attach some project file to it, if you aren't using projects - this can be a problem.
then for any other back end stuff - I'm a fan of SQLTables and SQLColumns write a quickie routine to populate sqltables, then scan..endscan on sqltables output with SQLCOLUMNS to create meta-info, tables, etc on each table in the backend. I start with these 3 things when I have to reverse engineer something, then 'get serious' with a 'paid product' if I can't figure it out, or need 'long-term maintainability' of a 'data dictionary' or 'entity-relationship diagram' Finally, there's also an option to 'generate sql code' in any database container - but if yer not using DBCs, this isn't so useful - the prep work to make a dbc just for documentation purposes might seem overwhelming to you (or easy, if you know how to do it via code). I dunno, I got hooked on FoxDoc() ages past, and use pieces of that output, still, when managing some codebase. HTH ! -- William Sanders / efGroup _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
