which way is the best? 1 big script or many little scripts?

[glzm0]

hello out there

I have a few questions. Which way is the better one for scripting?

Should I use one big script for my database? I jump then to the right position with scriptparameters.

Or should I have many little scripts which I call like the normal way when I need them?

What is better for the performance of the database.

[mr_vodka]

As a general rule, if a set of script steps can be reused frequently, then it makes more sense to keep those as a seperate step; which in turn can be used as a subscript.

[Ender]

I'd say go with one script for each major operation, but if there are parts that are similar for different record sets or something, use subscripts for those (pass parameters as necessary).

For example if you have a bunch of reports, they might all start out putting the user into a Find screen, and they might all end with a print preview, but in the middle, they do different things to Find specific subsets, go to the right layout, and sort based on specific fields. So I'd use separate scripts for each report with subscripts to do the common operations, like enter the Find screen and set some default criteria, then manage the whole Print/Preview operation.