You know what, Dennis, that's not a bad idea... Usually I am using C&P because I want to make sure I have the same fonts, colors, etc. And different clients have different schemes so I could have a "cheat sheet" form stored on each client's database. It gets especially tricky when you're copying something complicated like a list view from one form to another.
I always have a "defaults.klt" program stored at each client that has their favorite way of doing things like dialog boxes, choose lists, print statements, program closing code, etc. This would carry my defaults one step further! Karen In a message dated 1/27/2012 10:49:42 AM Central Standard Time, [email protected] writes: > Why not make a sample form. > > Fill it with all the controls you use, set up you favorite ways, but with > blank componentids and no code or variables or lookups. > > Basically make them C&P idiot proof! > > You can continue to optimize, add to and enhance these as you wish. > > > > You can C&P these without getting into trouble. > > If you need multiple forms with controls set up for different scenarios > that is obviously a possibility. > > > > You can even carry them unloaded to a usb stick for use at customer > sites! > >
