vb6 to .net 05 and sheridan controls

[Ed.]

Hey All,
We are currently upgrading a vb6 development to vs.net. We use the
sheridan datawidgets v3 ocx extensively throughout the program. My question
is, can you generally use older 3rd party ocx in an application, and has
anyone any experience in doing this with the sheridan datawidgets? If so,
did it work?

Posted this accidentally to the old vb6 group first - sorry for the
cross-post.

All the best,
- Ed

[Cor Ligthert [MVP]]

Ed,

Crossposting is for the dotNet newsgroups no problem, however, why do'nt you
try it and tell us than what your problems are, that is a kind of
interactive learning and that is for most of us were these newsgroups are
for.

Cor
"Ed." <ti******@hotmail.comschreef in bericht
news:45********@quokka.wn.com.au...

Hey All,
We are currently upgrading a vb6 development to vs.net. We use the
sheridan datawidgets v3 ocx extensively throughout the program. My
question
is, can you generally use older 3rd party ocx in an application, and has
anyone any experience in doing this with the sheridan datawidgets? If so,
did it work?

Posted this accidentally to the old vb6 group first - sorry for the
cross-post.

All the best,
- Ed

[Ed.]

Hello,
Thanks for the reply. We have actually opened the project and have found
over 100 issues, and it tells us it has reached the maximum that it can
display, so I assume there may be MANY MANY more.

We were hoping that an upgrade would involve some fixes here and there but
there are many issues, most of which we simply do not understand as the
syntax and usage for some things seems so different. I'd suspected this may
be the case but we needed to see for ourselves.

I am still trying to get my head around a couple of issues - I will most
likely post again once I have - I don't want to waste the time of others
unless I am stuck.

One question though, can old vb6 style ocx generally be used within vb.net
2005?

Thanks - L

"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:u4**************@TK2MSFTNGP02.phx.gbl...

Ed,

Crossposting is for the dotNet newsgroups no problem, however, why do'nt
you try it and tell us than what your problems are, that is a kind of
interactive learning and that is for most of us were these newsgroups are
for.

Cor
"Ed." <ti******@hotmail.comschreef in bericht
news:45********@quokka.wn.com.au...

>Hey All,
We are currently upgrading a vb6 development to vs.net. We use the
sheridan datawidgets v3 ocx extensively throughout the program. My
question
is, can you generally use older 3rd party ocx in an application, and has
anyone any experience in doing this with the sheridan datawidgets? If
so,
did it work?

Posted this accidentally to the old vb6 group first - sorry for the
cross-post.

All the best,
- Ed

[Tom Shelton]

On 2007-01-16, Ed. <ti******@hotmail.comwrote:

Hello,
Thanks for the reply. We have actually opened the project and have found
over 100 issues, and it tells us it has reached the maximum that it can
display, so I assume there may be MANY MANY more.

We were hoping that an upgrade would involve some fixes here and there but
there are many issues, most of which we simply do not understand as the
syntax and usage for some things seems so different. I'd suspected this may
be the case but we needed to see for ourselves.

I am still trying to get my head around a couple of issues - I will most
likely post again once I have - I don't want to waste the time of others
unless I am stuck.

One question though, can old vb6 style ocx generally be used within vb.net
2005?

In general, yes they can.

--
Tom Shelton