Hi all, I have an install where it may need to run SQL scripts on up to 2 different SQL servers. I feel pretty comfortable collecting the information for one of those four with a UI screen, but I'm hoping to reuse the screen for all SQL Servers. From what little I know about UI development in an MSI, this seems to be pretty difficult, because you're essentially hardcoding property names for your various UI screens to push data to, and the installer uses the data from there. How can I use the same screen to push to a different set of properties?
I was looking for suggestions on the cleanest way to approach this so that maintenance down the road is easy (should we add a 3rd or 4th SQL server, for example). Is there a dynamic way to do it, or is it better to statically code? Thanks, -Jeff ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
