Access Analyzer & Documenter

[Peter Hallett]

Dirk,

I am very grateful for that. Don’t worry about any ‘roughness’ of the
result. The last lot ran just fine, almost straight off the page. In any
case, it will be a great deal easier for me to do a bit of debugging than to
start from scratch.

I don’t suppose that the result will be ready for a while. I have got
another big job running at the moment and I expect I might have to pose one
or two questions from time to time, if you don’t mind.

In the slightly longer term I have got some ideas without, at present,
having much idea of how to implement them. The Help file is working
overtime. I have clearly got a lot to do but I will certainly submit the
result for others to pick-over, or use. It’s beginning to look as if this
could be a really useful tool.

Finally, it would seem that you and I are now the only ones left on this
thread. Shall I turn out the light, or will you?

 

[Clif McIrvin]

Dirk -- using OE as newsreader ...

<quote>
If InStr(.RecordSource, strSought) Then
Debug.Print "Report " & .Name & " RecordSource: " &
..RecordSource
lngFoundCount = lngFoundCount + 1
</quote>

 

[Dirk Goldgar]

Dirk -- using OE as newsreader ...

<quote>
If InStr(.RecordSource, strSought) Then
Debug.Print "Report " & .Name & " RecordSource: " &
.RecordSource
lngFoundCount = lngFoundCount + 1
</quote>

Thanks, Clif. It seems to be Microsoft's forum software. I've gone here to
view it:

http://www.microsoft.com/office/com...8ada&catlist=&dglist=&ptlist=&exp=&sloc=en-us

.... and there are two dots on the broken line as it appears there. That's
not good, and I'll have to report it to them as a bug.

 

[Dirk Goldgar]

Finally, it would seem that you and I are now the only ones left on this
thread. Shall I turn out the light, or will you?

<click!>

 

[Clif McIrvin]

Thanks, Clif. It seems to be Microsoft's forum software. I've gone
here to view it:


http://www.microsoft.com/office/com...8ada&catlist=&dglist=&ptlist=&exp=&sloc=en-us

... and there are two dots on the broken line as it appears there.
That's not good, and I'll have to report it to them as a bug.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

You're welcome.

As expected, when I followed the above link, I also found the two dots.

 

[Thomas (ADC)]

As the author of the aforementioned tool, I would like to humbly
announce that the described misbehaviour has been fixed in the latest
release (0.9.3). Inspired by this thread I have also added a feature
to detect the use of custom VBA functions in queries and other SQL-
based objects.
If you encounter problems using the tool, miss coverage for a type of
link or have ideas for other features, please contact me thru the
website. As this project is open source by purpose, all kind of
support will be appreciated.

 

[kate]

It's not worth buying standalone, but I get Visual SourceSafe as part of
an MSDN subscription, so it's "free", meaning I already paid for it.

I think there are some VSS-compatible programs, at least one of which used
to be free for a single-user license. I think those would also work.
Here's one of them, which says it is free for a single user:
http://sourcegear.com/vault/?gclid=CPmc59Ocv5oCFQOuFQod5nYVtA

I haven't used any of the alternatives, but my understanding is the Access
sourcecode control add-in should work with them.