Linked Tables Question

[tps131]

I was given this working database with all linked tables and a back end to work on and configure for a project. I was wondering how without corrupting the data in the tables you can tell where the updated information is being sent?

 

[hneal98]

Where what updated information is being sent? Not sure what you are asking.

 

[tps131]

The program has extensive forms for user evaluation of software vendor requirements. I am wondering the process of the information flow from that form to the front end and then from there to the back end. Is there anyway to physically see the flow of information and what is linked to what?

 

[hneal98]

There is a reporting feature that will tell you all of the names of tables, queries, etc and what depends on what. Not sure if that is what you need, but if you are using Access 2000 or greater, you can do that from the Tools menu under Analyzer|documenter.

See if that is what you need. Earlier versions also have the documenter, but I don't recall how to get to it since the menu system is different.

 

[willir]

It sounds like you want two things, although you only suggest one...
- how much data is being created?
- where is the data being stored?

First, in "Getting to know your database, 101", use the Documenter. (From the menu, "Tools" -> "Analyze" -> "Documenter") This tool is absolutely essential in that it reports information on...
- tables (ODBC linked, fixed-linked, etc)
- field names and properties
- security
- relationships
- date table was created and last updated
- indexes
...But sadly, does not report number of records or transactions
...Warning - the reported generated can be 100's of pages long. It may take some serious resources to run.

Another really useful tool is the Relationships gui window (from the menu, "Tool" -> "Relationships") Gives you a graphical representation of the schema.

As far as tracking transactions. You can create some simple tools...
- SELECT Count(*) FROM TableName to gather record counts. Running this peridocally will give you a sense of usage
- If there is a date field on the table, you can use the Date field to report historical activity, SELECT Count(*) FROM TableDate WHERE Month(DateField) = ...
or... GROUP BY Month(DateField), etc

To get an idea on the size of data a table has, add up the size of each field (and text fields and objects are tough to guess-timate) * number of records + space used by indexes + some administrative over head.

Although this is not specifically want you want -- to see the data being written -- it should help you accomplish the administrative tasks required of you.

Good luck.
Richard