Some erros while opening a project.

Hi group,

I've been programming on MS Access 2000 for about 6 months.
And i've thought it could be like VB6.
So, the trouble:
I have a Visual Basic 4 project, and i'm trying to open it on VB6.
I've opened the project, and the followings error acurried:

Line 221: Class Threed.SSCommand of control Incluir was not
a loaded control class.
Line 285: Class Threed.SSPanel of control Barra was not a
loaded control class.
Line 184: The property name _Version in Barra is invalid.

########
Compile Error:

Procedure declaration does not match description of event or procedure
having the same name

########

spin32.ocx
threed32,ocx
grid32.ocx
crystl32.ocx

So, it's basically 3 troubles...
May someone give some instructions?

The project should be working on VB4 without any troubles

Rodolfo Fontes wrote:
> Hi group,
>
>     I've been programming on MS Access 2000 for about 6 months.
>     And i've thought it could be like VB6.
>     So, the trouble:
>         I have a Visual Basic 4 project, and i'm trying to open it on
VB6.
>         I've opened the project, and the followings error acurried:

That can happen for several reasons. If the ocx isn't registered or the
oca file is damaged in one way or another, you'll see that "not loaded"
error.

Find out what ocx's you need, start a new VB6 project and drop one of
each on the form. If that works, you know that the components are 'ready
for use'. At that point, it's just a matter of getting the VB4 source to
use them. That may require that you manually edit the frm file (and
project file).

> Compile Error:
>
> Procedure declaration does not match description of event or procedure
> having the same name

This means that the event declaration for the component you're using
doesn't match the one that was there in the first place. This is usually
easy to fix. You can get that error by loading a Common Controls 5
ListView (for example), adding code to its event handlers and then
switch to a Common Controls 6 ListView. Same events but they have
different arguments.

To fix that, find out which events you're using for that control, start
a new project and drop the new control on the form. Double-click it to
show the event handlers and select the same event(s) you have in your
'working' app. Copy and paste the arguments from your test app to your
working app. Below, you'll see the difference in the ListView controls I
mentioned... Note that the 2nd one (the v6 control) shows "MSComctlLib"
instead of "ComctlLib".... all it would require in this case is to
change the "ComctlLib" to "MSComctlLib".

'Common Controls 5
Private Sub ListView1_ColumnClick(ByVal ColumnHeader As
ComctlLib.ColumnHeader)

End Sub

'Common Controls 6
Private Sub ListView1_ColumnClick(ByVal ColumnHeader As
MSComctlLib.ColumnHeader)

End Sub

btw. Make sure you create a backup of the project before doing any of
this and make sure you don't save a form if it reports the "not a loaded
class" error. When it reports that error, it changes all of the controls
of that type to PictureBoxes... which means that you'll need to do more
work to get things going.

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..