Questions on workbench versioning

[#1]

I learned the hard way that one should not really be using designer in workbench to modify forms, due to the version incrementing with each save and possible database bloat that could result.  Knowing that, the following questions come to mind:

1.  Can I limit the number of versions of a form that are stored?
2.  Can I clean out older versions of a form??
3.  When I delete a form (or file) from the resources pane, let's say it's at version 15, are all previous versions of that file deleted too?  Or do they hang around in the tables as orphans?

If the answers to questions 1 and 2 are "no", then I would really like to see a utility, perhaps in adminUI, to handle this.

Thanks!

Elaine

[#2]

Um, I don't quite get it. (And no, I haven't tested this...)

Are you saying that if you:

1. Delete the fragment
2. Upload a new version of the fragement
3. Open the XDP form that refers to the fragment

--> You get the old version of the fragment?

   4.   But if you close workbench, then open it again, and then open the XDP form

--> You get the new version of the fragment?

If that's the case, it sounds like a simple caching issue in Workbench - it's not refreshing the cached copy of the fragement.

And in fact, this actually makes sense, because the version number of the replaced fragment is the same (or lower) than the original fragment.

Is this what you're saying?

The really interesting issue is whether this same caching problem will occur on the server when you render the form?

Howard