> I guess whats frustrating to me is that I can put together a basic
> system in VFP if I develop it from scratch, but this system I'm working
> on with no documentation where they have security, oracle and sql server
> backends is kicking my butt and I still havent been able to sucessfully
> trace my way through the program which is usually how I learn things.
First thing you want to find out is how much procedural, how much oop.
Do they generally have their code in PRGs, SCXs or VCXs? (Usually a
combination of all three...)
So the first thing I do with a new system (new to me, old to the other
guy) in order to figure out what's going on is to trace the code... by
using my very favorite command, debugout. The important trick here is to
identify WHAT function you're in when you use it. For example, instead
of just typing
debugout 'mid-way through the main prg, about to run the login screen'
you want to put things like
debugout 'main.prg: about to run login.scx'
debugout 'main.prg: done running login.scx, about to check permissions'
debugout 'main.prg: about to run table-opening function'
so then in your debugout window, you can see what's happening.
Then, in login.scx, you put debugout code in any method that already has
done (watching for lpara statements, of course <s>):
debugo 'login.init(): loading form'
debugo 'login.init(): about to populate combo box arrays'
that sort of thing.
I'm sure this won't help as much as it ought to, but it should be enough
to get you to answer the next question.... <s>
Whil
©2007 Whil Hentzen (Pro*) |
