I need someone who can help me with some customizaton of the open dialogue box of a windows financial accounting application. The application on launch shows a window listing all files opended in that application in the the past so that one can select from this dialogue box which file to open now. I want that this dialogue box that opens automatically on start of the application does not remember which of the files were opened in the past and I want that this list of old files opened in the past should not be visible from this window.d I do not mind if this dialogue box does not appear at all. Similarly, the "Open previous file" command (under the file menu should not display the previously opened files) On the other hand, one should use the open command from the File Menu of the application to access a folder to select and open a file. So, probably a script can clean up its memory every 15 minutes or so, so that it starts from a blank state. Any other method which is appropriate will be acceptable and which would not amount to violation of the licensing policy of the software vendor. To further understand what I am saying, please visit [url removed, login to view] server name: [url removed, login to view] username: demo password: demo123 You will see the application running on terminal services with an Open dialogue box showing the list of files opened in the past. Since it is a demo and if someone has left a file open, then please go to the File menu and select close to close the open file. As soon as the open file is closed, the dialogue box that I am talking about will appear for you to see - to allow you to select another file that was ever opened in the past. Later on I will make available full access to the server to let the selected coder check the various parameters and suggest appropriate changes to get over this problem. The following is an addition to the original Request for Bid Solution to the problem lies in tackling the .ini file which contains the list of Most Recently Used Files (MRU Files) A sample of the .ini file is attached. So, if this file can be cleaned up regularly, at a given interval so as to not have the listing of MRU files, I believe that should solve the problem Thanks
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request.
Windows 2003 server. I think what works on Windows 2000 will work on Windows 2003 server also.