Welcome, Guest. Please Login
Tinderbox
  News:
IMPORTANT MESSAGE! This forum has now been replaced by a new forum at http://forum.eastgate.com and no further posting or member registration is allowed. The forum is still accessible via read-only access for reference purposes. If you wish to discuss content here, please use the new forum. N.B. - posting in the new forum requires a fresh registration in the new forum (sorry - member data can't be ported).
  HomeHelpSearchLogin  
 
Pages: 1
Send Topic Print
Documenting Access Database (Read 2564 times)
Simon Knight
Full Member
*
Offline



Posts: 80

Documenting Access Database
Nov 11th, 2013, 4:14am
 
I have a task to document a complex Access Database.  I have started using Tinderbox for my notes and am wondering if Tinderbox is powerful enough to do more for me.  I am able to extract TSV data from the Access database that describes its design and propose adding this information to a Tinderbox file.  I would like to list the major components along with their data sources in an attempt to identify unused objects.  For instance, if I create notes about queries and include an attribute that lists all the data tables that the query uses is it possible to create agents that list all the queries that use a certain table?

best wishes

Simon
Back to top
 
 
  IP Logged
Mark Anderson
YaBB Administrator
*
Offline

User - not staff!

Posts: 5689
Southsea, UK
Re: Documenting Access Database
Reply #1 - Nov 11th, 2013, 9:30am
 
In short, Yes! How much extra metadata you need to apply (i.e. user attributes) will depend on whether existing text you import produces notes with sufficiently unique data to query.

Worst case, you may need to add user attribute(s) to allow you 'tag' notes with a term for which it is easy to query. Trivial example - you want to look for 'XYZ' but many notes you don't want also hold that value. Make a String attribute and store 'XYZ' - or some suitable value, in the attribute for the relevant notes.

Tip. After you've done an import of the data, make a copy of the TBX document using a new name. Open the latter and delete most of the new data. Leave only enough for you to be able to design and test representative agents, prototypes, etc. The temptation is to dive straight in. That may work, but if not this approach of using a smaller dataset to help figure the code you need can be very helpful. As you figure what's needed you can then implement the ideas in you full data file.

Does that help?
Back to top
 
« Last Edit: Nov 11th, 2013, 9:31am by Mark Anderson »  

--
Mark Anderson
TB user and Wiki Gardener
aTbRef v6
(TB consulting - email me)
WWW shoantel   IP Logged
Simon Knight
Full Member
*
Offline



Posts: 80

Re: Documenting Access Database
Reply #2 - Nov 11th, 2013, 11:05am
 
Yes that helps and thanks for the tip.

Simon
Back to top
 
 
  IP Logged
Pages: 1
Send Topic Print