Mouse wheel, XP, and VB5

[Woof-Woof]

Why doesn't my mouse wheel work in the code windows in VB5 under XP?
I can scroll the properties and project windows using the wheel, but
not the actual code windows (XP). Everything works fine using Windows
98.

Thank you.

---
Allen

[Jos]

"Woof-Woof" <ot*********@cox.net> wrote in message news:<iIKxc.7058$fZ1.330@fed1read03>...

Why doesn't my mouse wheel work in the code windows in VB5 under XP?
I can scroll the properties and project windows using the wheel, but
not the actual code windows (XP). Everything works fine using Windows
98.

Thank you.

---
Allen

AFAIK the mouse wheel has never worked in VBA code designer.
Just another of those petty annoyances of life.

Jos

[J French]

On 10 Jun 2004 06:08:02 -0700, jo***********@yahoo.co.uk (Jos) wrote:

<snip>

AFAIK the mouse wheel has never worked in VBA code designer.
Just another of those petty annoyances of life.

We are talking VB5 here

Or are you saying (correctly) that MS view VBx as a VBA Designer ?

[Steve Letkeman]

if my DLL declaration looks like this
Private Declare Function Test1Func Lib "testdll.dll" (ByVal Num As Integer)
As Integer

is there a way to make the DLL name variable, as in

Dim DName as string
DName="testdll.dll"
Private Declare Function Test1Func Lib DName (ByVal Num As Integer) As
Integer

Thanks,
S

[J French]

On Fri, 11 Jun 2004 20:53:52 GMT, "Steve Letkeman"
<us*********@zanthic.com> wrote:

if my DLL declaration looks like this
Private Declare Function Test1Func Lib "testdll.dll" (ByVal Num As Integer)
As Integer

is there a way to make the DLL name variable, as in

Dim DName as string
DName="testdll.dll"
Private Declare Function Test1Func Lib DName (ByVal Num As Integer) As
Integer

Not as you want to do it.

One can use the API LoadLibrary to load a DLL by name
However you will have problems calling the functions as VB does not
natively support calling functions by address.

What is it that you really want to do ?

[Steve Letkeman]

Thanks for your response. What I want to do is assign a DLL
at run time so I can add DLL's later on without having to change
the program. Each DLL will have the same function names and
method of calling them, just different file names.
I would store the DLL file names in a startup file and just
modify that when a new DLL is added.
Are you suggesting that if the function names are constant
then the API LoadLibrary would work?

Steve

"J French" <er*****@nowhere.com> wrote in message
news:40***************@news.btclick.com...

On Fri, 11 Jun 2004 20:53:52 GMT, "Steve Letkeman"
<us*********@zanthic.com> wrote:

if my DLL declaration looks like this
Private Declare Function Test1Func Lib "testdll.dll" (ByVal Num As Integer)As Integer

is there a way to make the DLL name variable, as in

Dim DName as string
DName="testdll.dll"
Private Declare Function Test1Func Lib DName (ByVal Num As Integer) As
Integer

Not as you want to do it.

One can use the API LoadLibrary to load a DLL by name
However you will have problems calling the functions as VB does not
natively support calling functions by address.

What is it that you really want to do ?

[J French]

On Sat, 12 Jun 2004 18:14:23 GMT, "Steve Letkeman"
<us*********@zanthic.com> wrote:

Thanks for your response. What I want to do is assign a DLL
at run time so I can add DLL's later on without having to change
the program. Each DLL will have the same function names and
method of calling them, just different file names.
I would store the DLL file names in a startup file and just
modify that when a new DLL is added.
Are you suggesting that if the function names are constant
then the API LoadLibrary would work?

Are you writing these DLLs yourself
- and if so in which language ?

If you are writing 'real' DLLs yourself then what you want to do is
pretty easy, you will just need to write another DLL that contains
procedures/functions that can call other procedures/functions by
address.

[J French]

On Sun, 13 Jun 2004 06:54:27 +0000 (UTC), er*****@nowhere.com (J
French) wrote:

On Sat, 12 Jun 2004 18:14:23 GMT, "Steve Letkeman"
<us*********@zanthic.com> wrote:

Thanks for your response. What I want to do is assign a DLL
at run time so I can add DLL's later on without having to change
the program. Each DLL will have the same function names and
method of calling them, just different file names.
I would store the DLL file names in a startup file and just
modify that when a new DLL is added.
Are you suggesting that if the function names are constant
then the API LoadLibrary would work?

Are you writing these DLLs yourself
- and if so in which language ?

If you are writing 'real' DLLs yourself then what you want to do is
pretty easy, you will just need to write another DLL that contains
procedures/functions that can call other procedures/functions by
address.

Further info:
I suggest that you look at the downloadable API Guide from
www.AllAPI.net

Have a look at the CallWindowProc information
- then the example of using it called 'Register Server(2)'

You would also be wise to dig around for the Win32 Programmer's
Reference Help File that should come with VB

Watch out though, CallWindowProc only works with 5 parameters despite
some misleading stuff in the documentation.

[Steve Letkeman]

I want to write the DLL in VB6 but have the capability to use
C if I want to make an intermediate DLL. Just to clarify one point,
I'm not wanting to use variable function names, just the DLL file name
itself. In VB.net you can specify the DLL file name as a variable and
call a function in a VB.net created DLL or a C DLL but you can't
call a VB6 created DLL (which is what I really want to do) At this
point the calling program will be VB.net but the DLL's would be
best to be VB6.
One option would be to have the VB.net program call the C DLL
with the variable DLL name and the C DLL is hardcoded to call
the VB6 DLL, kind of a kludge though.
Steve

"J French" <er*****@nowhere.com> wrote in message
news:40****************@news.btclick.com...

On Sat, 12 Jun 2004 18:14:23 GMT, "Steve Letkeman"
<us*********@zanthic.com> wrote:

Thanks for your response. What I want to do is assign a DLL
at run time so I can add DLL's later on without having to change
the program. Each DLL will have the same function names and
method of calling them, just different file names.
I would store the DLL file names in a startup file and just
modify that when a new DLL is added.
Are you suggesting that if the function names are constant
then the API LoadLibrary would work?

Are you writing these DLLs yourself
- and if so in which language ?

If you are writing 'real' DLLs yourself then what you want to do is
pretty easy, you will just need to write another DLL that contains
procedures/functions that can call other procedures/functions by
address.

[J French]

On Mon, 14 Jun 2004 16:20:13 GMT, "Steve Letkeman"
<us*********@zanthic.com> wrote:

I want to write the DLL in VB6 but have the capability to use
C if I want to make an intermediate DLL. Just to clarify one point,
I'm not wanting to use variable function names, just the DLL file name
itself. In VB.net you can specify the DLL file name as a variable and
call a function in a VB.net created DLL or a C DLL but you can't
call a VB6 created DLL (which is what I really want to do) At this
point the calling program will be VB.net but the DLL's would be
best to be VB6.
One option would be to have the VB.net program call the C DLL
with the variable DLL name and the C DLL is hardcoded to call
the VB6 DLL, kind of a kludge though.

Right, you have just moved the goalposts

You started off talking about :

Private Declare Function Test1Func Lib "testdll.dll" (ByVal Num As
Integer) As Integer

Which is the declaration for a 'real' DLL

What VB makes is ActiveX DLLs, which are basically VB Classes wrapped
in their own separately compiled code.

Dim X As Object

Set X = CreateObject( "DllInternalName.ClassName" )

The above is an example of late binding
Note: the AX DLL needs to be registered