Hi David: Cant help, sorry. This is the type of headache that can give you gray hair - mine is silver after many years of these types of encounters. It went gray over 20 years ago when I was still a COBOL Programmer - no kidding, gray at 40! There were many 24 hour days when implementing a new project and thigs didn’t deploy as expected. I worked in Health Care and Finance so the systems needed to just flat out work when the client fired it up the first time - if not it was 24 hours, 48 and beyond on a couple of large projects, until it did work perfectly. The Michigan Lottery, first one, comes to mind. We handled the software for it and when we ran the final test the day before it was to go live, tv, radio and all that jazz was involved, the project failed and we were up all night, flew in a specialist and got it up before the first drawing in the morning! Ya, a few more gray hairs - sigh. Later and good luck with the project.Rick USA
-----Original Message----- From: David [mailto:trailerda...@hotmail.com] Sent: Thursday, January 1, 2015 6:07 AM To: gw-scripting@gwmicro.com Subject: How to fix a messed up wepm file? All you experienced developers, I sure could use a bit of help here. Smile. OK, it just had to happen. We are all imperfect, and things sometimes goes a bit faster than our brain. Smile. I released a new version of the Extended Dictionary yesterday. Version 0.69. It is meant as a replacement for 0.68. Users report it installed just fine, and everything seems wonderfully well. Then, this morning one user got in touch with me, and reported that he has two entries of the Extended Dictionary, showing up in the Package Manager. That is, if you go to WE Controlpanel, and hit Alt-A, Right-Arrow, and once Down-Arrow - where it says to Add and Remove apps. Hit enter here, and in the list, both version 0.68 and 0.69 will show up. I had to troubleshoot a bit, and it seems that I made one simple typo, in my creating the 0.69 wepm archive. For some reason, the wepm file shows up to be named "zExtended Dictionary", whereas it should have been named the same as always before: "Extended Dictionary". That little extra Z-character that had made its dirty way into the filename, causes things to show up as two different entries in the Package manager. I Thought things now would be as easy as to ask the user to remove the old entry of 0.68. But when I tried it myself, the package manager all the sudden removes both the entries, and the user looses the app. Allright, I thought, now just let him reinstall the package. but then the new install will get the wrong wepm filename attached. Sure, I will upload a fixed version of the wepm file, but is there a way for my app to remove the wrongly spelled wepm archive, and thereby cleaning up the user's Package Manager? Or, will I have to ask everyone who has installed the 0.69 version, to perform some manual steps here, to get things cleaned up? If there is an automated way, I would much prefer that, so as to have the user as little confused as possible. For those on the list, who happen to run the package, I do apologize for the inconvenience hereby caused. It is all due to my mistyping the filename, and I should have made better proofreading prior to the upload. I just want to know, if there is an easy fix from here. For anyone who has a bit of feedback here, thanks for all you can provide. And to the AISquared staff, if there is no easy way for my app to automatically remove all its "double entries" from the package manager, is there a way that such feature could be implemented for later cases? Thanks, and apologies, -- David
