Matt,

Thank you ver much for your very elborate reply.
I think the #Alias dictionary is the way to go for me. I'm not so sure whether it will work out well that the objects are created automatically in the background, but I'll give it a go.

Walter


>Oh, and I also forgot to tell you about this real goodie!!
>
>Let's say you are coding along with an object reference to a class, and you want Thor Intellisense on it.
>
>Your local code reference is: "loMyFancyObject"
>
>Well, add this to the top of your method:
>
>*#Alias loMyFancyObject = {TheClassName, TheClassLib.vcx}
>
>or, if your class is defined in a prg:
>
>*#Alias loMyFancyObject = {TheClassName, TheProcFile.prg}
>
>
>Now!!! if you type loMyFancyObject and then [dot], and then invoke the Thor IntellisenseX hotkey, it will see where to find the object and it will create one in the background, and give you intellisense!!
>
>Of course, you will have to make sure the vcx/prg can be found in the current PATH assignment so it can find them
>
>Cool, huh?
>
>Even further of awesomeness is that you can add that *#Alias definition to the Alias Dictionary, and it will be available all over the place and you do not have to add the explicit *#Alias definition each time.
>
>So, as long as you consistently use the same object reference names for you objects, the Alias Dictionary is very helpful.
>
>
>And, if you use the "Custom Keyword List" tool, you can even get CapitalizedMethodNames and PropertyNames to match your actual code if you cased them there.
>
>
>There is a lot it can do, but you have to know how to configure it. I have to admit it is very obscure, but to be fair to Jim Nelson, it has gotten so complex (i.e. powerful/thorough), it's really hard to communicate what all it can do and how to do it, but he really did a lot of work to create pages on VFPX and even made a lot of videos. I had the luxury of working with him while he developed it, so I got some really forensic help and training from him along the way. Hopefully I can pass some of it along to you.
>
>Jim Nelson, the author, did a SouthWestFox session on Thor IntelliseseX in 2014. If you were there, you can find the white paper on your CD. If you join the Google Group and ask him for it there, I am sure he would send it to you.
>
>
>
>>I know I'm late in the game of looking into Thor, but looking into the youtube videos I see that it can be very useful for me.
>>
>>However, two of my most important problems don't seem to get solved. Please tell me I'm wrong on this.
>>
>>You cannot easily use intellisenseX on public objects. For example I've got several public objects
>>Applic: The global Applic object which can be referred to in any piece of code.
>>oPS: Personal Settings
>>oDatacache: Responsible for caching remote data
>>oDF, Datafunctions, Applic specifig function to create lookups
>>etc...
>>
>>They not specifically declared other than in the places where they are created, but I really like to use intellisense on them anywhere in my project.
>>Is there a way to do this?
>>
>>
>>The other question is whether it is possible to easily save all thor tools and settings to be applied to another development machine. Personally I've got 2 desktops and 2 laptops which I use to code and I really hate to install and configure things on all 4 machines. Is there a way of doing that?