On Sun, 16 Jan 2005 23:27:32 -0800, you wrote: >1. What does your comment have to do with my comment. I am talking about >the DATA file not the application
I chose your reply to the orginal poster by mistake. Clicked on the wrong reply but I suspect most people know what I'm referring to. >2. As designed, it will install files that it needs to the OS folders. It needs Microsoft VB files and likely, that's it. That's typical of a Visual Basic application. I'd be VERY surprised if LEGACY is installing ANYTHING of its own into OS folders. >you rely on another computer to have the correct version of these runtime >files, you could be asking for data corruption. I wouldn't rely on this nor >would I recommend anyone else do so. I thought you said you were an old >developer. If you really are, you would know this. I've been in development since 1978. I know what I'm talking about Glenn. Please quote where I said you recommended people run this way. I simply said I believed you COULD run Legacy from a Flash Drive IF the correct VB files happened to be installed on the computer in question. I've seen this work MANY times (and also have seen it not work many times) generally dependent on just how many components or controls Legacy might be using aside from the defaults. They might also be using a third-party control and that would not be installed. In no way did I say that someone should go ahead and work this way. I simply was pointing out that this current limitation really isn't one that the Legacy coders wanted. It's an unfortunate by-product of the application they chose to develop in. I guarantee you that, if given the choice, the Legacy folks would MUCH prefer that Legacy not install all this garbage all over the system. It makes for a much cleaner, much more portable, much easier to support product. As it is, if Legacy depends, for example, on a Grid Control of a specific version and then another VB app comes along and installs a newer, but incompatible control, the OS is going to let it happen because it's newer. Legacy didn't do anything wrong but now this Legacy user won't be able to get Legacy to work properly because they installed something else that happened to use a newer version of that control. I am also certain that Legacy support has had this exact situation happen to them more than a few times. >In the future, please reply to the original note and make it relevant to the >topic in the note (top part) In the future, please have a modicum of flexibility in your dealings with people and not be so rigid as to feign not understanding a topic that is clearly understandable. Also please refrain from personal insults. I didn't insult you so please try not to insult me next time. As far as it being relevant to the topic, please re-read the subject of this very thread. The subject is, "Using Legacy with USB drive". I'm discussing that DIRECTLY. You're discussing data. If anything, I'm more on-topic than you are but you don't see me getting all up-in-arms and bent out of shape because you didn't respond specifically to the posters question. Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
