Taking a page from Reflection's, I recently had a project that required a report that would show what percentage of a wholesaler's clients meeting certain conditions. This information was constantly changing as we gathered more data. The project directors need to see this information for 850+ wholesalers throughout the day to make decisions. They also had tolerance levels set for these conditions. I set up an HP script menu system to allow the project director to run the report at will. The report was a comma delimited file which the script downloaded to the users PC after creation. The script then initiated a Reflection script residing on one of our servers. This Reflection script started Excel and ran a macro that imported the data into a shell xls file. The Excel file had VB macros that allowed them to manipulate the data in various ways, highlighted wholesalers that were below tolerance levels, etc. This gave the user much more power (and just as important, kept them from coming to me 4 times a day!). The data became more valuable because they could gain access to it at will and manipulate it themselves. Some of the problems we encountered were access rights to the server, version differences in Excel, and version issues in Reflection. > ---------- > From: Lars Appel[SMTP:[log in to unmask]] > Reply To: Lars Appel > Sent: Wednesday, August 16, 2000 1:48 PM > To: [log in to unmask] > Subject: Re: [HP3000-L] More Powerful and Prettier > > Sorry to refocus on the original question, but I would also be > curious to learn more about the use of / evolution to GUI or web > interfaces to the 3000, i.e. what tools people are using and in > what context, for what purpose. And, of course, what experiences > they can share (good or bad). >