Tom Shelton submitted this idea :
> GS explained :
>> Tom Shelton explained on 1/15/2012 :
>>> GS used his keyboard to write :
>>>> Tom Shelton formulated on Saturday :
>>>>> GS pretended :
>>>>>> Just want to interject that VB will persist to exist as the language of
>>>>>> choice for macros in MS Office. Since MS has reworked VBA to work in
>>>>>> x64 (VBA7), I don't expect VB to disappear in my working lifetime.
>>>>>> While it may be arguable that VBA is not Classic VB in various ways, it
>>>>>> remains that the underlying core to the VBA language IS Classic VB!<g>
>>>>>>
>>>>>> MS tried to take away VBA capability it Mac versions of MS Office and
>>>>>> got a horrific reaming for doing so. -Well.., at least enough of a
>>>>>> reaming that they put it back in pretty quick!
>>>>>>
>>>>>> I'm thinking there is not a dedicated special runtime for VBA, and so
>>>>>> unless I'm wrong MS will continue to ship that runtime with MS Office
>>>>>> if they take it out of Windows!<IMO>
>>>>>
>>>>> Not where I work - we use VS tools for office. VBA is banned.
>>>>
>>>> Yeah, I'm a big fan of using COMAddins over VBA. Though, I suppose the
>>>> .Net tools aren't really COM in the same way anymore. C++ is my choice
>>>> tool now but I'll use C# if .Net is really necessary. The nice thing
>>>> about C++ is that it still lets me use my 3rd party ActiveX components
>>>> that also work with VB6/VBA projects.<g>
>>>
>>> And you can use them in .NET as well... COM IS part of .NET.
>>
>> Not according to the manufacturer[s]. They recommend upgrading to their
>> .net versions. Has something to do with Windows Forms. If you can point me
>> to some info regarding using ActiveX components (in my case .OCXs) I'd
>> appreciate that very much.
>
> I've used AX components before... Simply add them to your toolbox - on the
> COM tab, and drag and drop them on the form. So, either the manufacturer[s]
> have done something really stupid (can't think what, because I haven't found
> one that didn't work - though, you might need to change your compile target
> to x86) or they are lying.

I'm thinking they just want to sell more product. I'll certainly try
your suggestion in C#. Big thanks...

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

GS formulated on Sunday :
> Tom Shelton submitted this idea :
>> GS explained :
>>> Tom Shelton explained on 1/15/2012 :
>>>> GS used his keyboard to write :
>>>>> Tom Shelton formulated on Saturday :
>>>>>> GS pretended :
>>>>>>> Just want to interject that VB will persist to exist as the
>>>>>>> language of choice for macros in MS Office. Since MS has
>>>>>>> reworked VBA to work in x64 (VBA7), I don't expect VB to
>>>>>>> disappear in my working lifetime. While it may be arguable
>>>>>>> that VBA is not Classic VB in various ways, it remains that
>>>>>>> the underlying core to the VBA language IS Classic VB!<g>
>>>>>>>
>>>>>>> MS tried to take away VBA capability it Mac versions of MS
>>>>>>> Office and got a horrific reaming for doing so. -Well.., at
>>>>>>> least enough of a reaming that they put it back in pretty
>>>>>>> quick!
>>>>>>>
>>>>>>> I'm thinking there is not a dedicated special runtime for VBA,
>>>>>>> and so unless I'm wrong MS will continue to ship that runtime
>>>>>>> with MS Office if they take it out of Windows!<IMO>
>>>>>>
>>>>>> Not where I work - we use VS tools for office. VBA is banned.
>>>>>
>>>>> Yeah, I'm a big fan of using COMAddins over VBA. Though, I
>>>>> suppose the .Net tools aren't really COM in the same way
>>>>> anymore. C++ is my choice tool now but I'll use C# if .Net is
>>>>> really necessary. The nice thing about C++ is that it still lets
>>>>> me use my 3rd party ActiveX components that also work with
>>>>> VB6/VBA projects.<g>
>>>>
>>>> And you can use them in .NET as well... COM IS part of .NET.
>>>
>>> Not according to the manufacturer[s]. They recommend upgrading to
>>> their .net versions. Has something to do with Windows Forms. If
>>> you can point me to some info regarding using ActiveX components
>>> (in my case .OCXs) I'd appreciate that very much.
>>
>> I've used AX components before... Simply add them to your toolbox
>> - on the COM tab, and drag and drop them on the form. So, either
>> the manufacturer[s] have done something really stupid (can't think
>> what, because I haven't found one that didn't work - though, you
>> might need to change your compile target to x86) or they are lying.
>
> I'm thinking they just want to sell more product. I'll certainly try
> your suggestion in C#. Big thanks...

Well, my guess is that they will work - but, I probably shouldn't have
been so terse in my response. There is always a possiblity that a
particular that something might go wrong in a new environment

--
Tom Shelton

Tom Shelton has brought this to us :
> GS formulated on Sunday :
>> Tom Shelton submitted this idea :
>>> GS explained :
>>>> Tom Shelton explained on 1/15/2012 :
>>>>> GS used his keyboard to write :
>>>>>> Tom Shelton formulated on Saturday :
>>>>>>> GS pretended :
>>>>>>>> Just want to interject that VB will persist to exist as the
>>>>>>>> language of choice for macros in MS Office. Since MS has
>>>>>>>> reworked VBA to work in x64 (VBA7), I don't expect VB to
>>>>>>>> disappear in my working lifetime. While it may be arguable
>>>>>>>> that VBA is not Classic VB in various ways, it remains that
>>>>>>>> the underlying core to the VBA language IS Classic VB!<g>
>>>>>>>>
>>>>>>>> MS tried to take away VBA capability it Mac versions of MS
>>>>>>>> Office and got a horrific reaming for doing so. -Well.., at
>>>>>>>> least enough of a reaming that they put it back in pretty
>>>>>>>> quick!
>>>>>>>>
>>>>>>>> I'm thinking there is not a dedicated special runtime for
>>>>>>>> VBA, and so unless I'm wrong MS will continue to ship that
>>>>>>>> runtime with MS Office if they take it out of Windows!<IMO>
>>>>>>>
>>>>>>> Not where I work - we use VS tools for office. VBA is
>>>>>>> banned.
>>>>>>
>>>>>> Yeah, I'm a big fan of using COMAddins over VBA. Though, I
>>>>>> suppose the .Net tools aren't really COM in the same way
>>>>>> anymore. C++ is my choice tool now but I'll use C# if .Net is
>>>>>> really necessary. The nice thing about C++ is that it still
>>>>>> lets me use my 3rd party ActiveX components that also work with
>>>>>> VB6/VBA projects.<g>
>>>>>
>>>>> And you can use them in .NET as well... COM IS part of .NET.
>>>>
>>>> Not according to the manufacturer[s]. They recommend upgrading to
>>>> their .net versions. Has something to do with Windows Forms. If
>>>> you can point me to some info regarding using ActiveX components
>>>> (in my case .OCXs) I'd appreciate that very much.
>>>
>>> I've used AX components before... Simply add them to your toolbox
>>> - on the COM tab, and drag and drop them on the form. So, either
>>> the manufacturer[s] have done something really stupid (can't think
>>> what, because I haven't found one that didn't work - though, you
>>> might need to change your compile target to x86) or they are
>>> lying.
>>
>> I'm thinking they just want to sell more product. I'll certainly
>> try your suggestion in C#. Big thanks...
>
> Well, my guess is that they will work - but, I probably shouldn't
> have been so terse in my response. There is always a possiblity that
> a particular that something might go wrong in a new environment

Wow... mangled that I was trying to say there is always a
possiblility of failure in a new envrionment - but, I must have been
thinking two sentences at a time....

--
Tom Shelton

Ok, I tried this and it's definitely a no-go. Not saying it's still not
doable, but rather a quick check didn't work for each of 3 components.
Looks like the C# environment doesn't like them, though. I'll try C++
when I get time...

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

On Fri, 13 Jan 2012 20:58:12 -0500, "Mayayana"
<(E-Mail Removed)> wrote:

>Tablets never made much sense in the first place,

I very much like my Kobo Vox 7" tablet. But then all I really do on
it is read eBooks and browse the web. I don't do much else with it.
I certainly don't type more than a sentence on it while in Facebook.

>so it's hard to know how that will work out. No
>matter how you look at it, people are not going to
>be writing docs and spreadsheets on a swipe screen.

Agreed. Although maybe with an external keyboard I can see some folks
using it to do some light work.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/