To continue support for the old apps of Rameses, may I suggest posting the docs for the old VB framework that was used?

Den, we will do our best to provide and post here the VB framework. If we can't produce it, you can post your issues on the proper forum and we will respond to it the soonest possible time. We are not just very good at documenting but we are practicing a proper documentation for our current projects. We learn our lesson of not having one

thanks.

Whatever purpose dennis has in mind, i don't think that posting the documentation on how the old tracs framework works, will not do good for the users like us. It will only add the burden if we try do understand the FRAMEWORK. Because of the ff. reasons:

1.The tracs framework is designed to be used by the programmer who created it. Its not designed to be used by ordinary users. (Same as a CAR, the owner does not need to know the knowledge on how to make an engine. He only need to know how to drive and do some little troubleshooting on his/her car).

2. It's more easier to understand the business process first before going to the core (framework) if our purpose of understanding the FRAMEWORK is to enhance the existing system. And it is less expensive if we do external enhancements rather than extending the old framework.

3. I understand that the old tracs frameworks is tightly design, meaning most of the components are integrated. So its dangerous to modify it, coz one procedural flaws will result to a domino effect on the other components.

I think the docs that are of importance to the cities include the documentation for extending the capability of the TRACS program such as the ad hoc report facility. As what I have observed, this capability is fully used by the Cities and allowing the creation of custom reports that can be plugged and be accessible within the TRACS program.

Other docs might include a complete documentation for the DataDef facility which sadly to say, we dont have.

A few comments though on Shalimar's observation.



Yes, the TRACS framework was designed for programmers but not just by the one who created it but for programmers who are willing to embrace the framework. Admittedly, the VB language fall short in providing a truly pluggable architecture therefore a truly pluggable module is not possible.



We highly recommend not extending the framework, rather, you extend the application if possible. Its true that extending the framework will take time and effort.



As with all frameworks, its always tightly designed to solve a particular programming problem. Its a well thought observation that a programming bug in any part of the framework possibly causes problem to other parts.