Question about SQL library - command objects

Hi,

I'm writing an application that uses multiple database tables. As a new basic4ppc user, it is not clear if I should use one single command object or if I should use multiple?

I've checked the exemple in the 'Basic4ppc and SQLite' chapter in the tutorial and I've seen that there's only one command object used over there.

The main reason why I'm asking this question, is because when following the 'good practices' you define the parameters via command.AddParameter and command.SetParameter. When having multiple SQL statements with multiple parameters, and only one command object, you keep on adding parameters to the command object. Is there a limit? Or are there some negative (performance?) issues about this? What about using mutiple command objects? Can this have a negative impact on the performance? Or is this not recommended?

Also in the exemple in the tutorial (e.g. Sub addOrder), there are some parameters defined (command.addParamater), meaning that on every execution of the Sub, these (existing) parameters are (re)defined. Shouldn't parameters be defined only once in a separate Sub? Or has this 'multiple redefinition' no impact at all?

Thanks for your feedback.

Filip

You can use multiple command object safely. A single command should also work. I don't think that you will encounter any performance issues from the unused parameters.