>What your ParameterAddSQL method does?

The framework has been built in a way to respond to various types of backends. So, no matter how I make it evolve, we shouldn't have to change anything in the client's application. So, by using this approach, this let the backend adjust the proper syntax at that level. As the parameterization is different between SQL Server and VFP, for example, the framework will then be able to adjust the SQL command before it will be executed against the backend. The same goes on with the ParameterAdd() method which will put in to a collection all parameters. Then, the proper SQL syntax is done. And, then, for debugging purposes, this opens the door to multiple valuable information based on the current data dictionary in place. For example, I can enable oProcess.lLogData to True. This will log into the Hit for the specific user, once the hit on the site has been completed, all the SQL commands that were executed, the elapse time it took and the number of records returned. Then, I can just cut & paste as is into SQL Server to execute it for testing purposes, such as you might have seen in several messages I have posted in this forum where you could see the parameterized approach I am using.