VB6 Problem

I had developed a VB6 application on my Win XP SP2 machine. Later my
HDD crashed and I have lost the source code.


I dont remember which version of MyODBC I was using. My mysql version
was mysql-4.0.18-win.

My application now gives me the following errors on windows xp sp2

run time error 383
text property is read only

Run time error '3705'
operation is not allowed when the object is open.

How do I eliminate these errors. I tried various older version of
MyODBC too but didnt got any sucess.

Thanks a lot.

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

RE: VB6 Problem

Not sure if this has any bearing on what you are doing, but I have seen
this message when trying to disconnect a server-side ADO recordset.
Only client-side ADO recordsets can be disconnected.



Randall Price
VT.SETI.IAD.MIG:Microsoft Implementation Group
" http://vtmig.vt.edu
+ Randall.Price@vt.edu
' (540) 231-4396

-----Original Message-----
From: Sawan Gupta [mailto:sawangupta.it@gmail.com]=20
Sent: Wednesday, December 28, 2005 7:24 AM
To: myodbc@lists.mysql.com
Subject: VB6 Problem

I had developed a VB6 application on my Win XP SP2 machine. Later my
HDD crashed and I have lost the source code.


I dont remember which version of MyODBC I was using. My mysql version
was mysql-4.0.18-win.

My application now gives me the following errors on windows xp sp2

run time error 383
text property is read only

Run time error '3705'
operation is not allowed when the object is open.

How do I eliminate these errors. I tried various older version of
MyODBC too but didnt got any sucess.

Thanks a lot.

--=20
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=3DRandall.Price@vt.edu


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

RE: VB6 Problem

Yes I have the MDAC 2.8 installed. I also ran WIndows Update and
system is fully updated with all patches.

What else should I check?

Thanks a lot.

Warm Regards,



On 12/28/05, Lu=EDs Damas wrote:
> Check if you have the last MDAC instaled (2.8)
> www.microsoft.com/data
>
>
> Regards
> Luis Damas
> ----- Original Message -----
> From: "Sawan Gupta"
> To:
> Sent: Wednesday, December 28, 2005 12:23 PM
> Subject: VB6 Problem
>
>
> I had developed a VB6 application on my Win XP SP2 machine. Later my
> HDD crashed and I have lost the source code.
>
>
> I dont remember which version of MyODBC I was using. My mysql version
> was mysql-4.0.18-win.
>
> My application now gives me the following errors on windows xp sp2
>
> run time error 383
> text property is read only
>
> Run time error '3705'
> operation is not allowed when the object is open.
>
> How do I eliminate these errors. I tried various older version of
> MyODBC too but didnt got any sucess.
>
> Thanks a lot.
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dsamad@mail.telep=
ac.pt
>
>
>
>


--
Sawan Gupta
sawangupta.it@GMail.com
http://www.SawanSoft.com
(+91)9829124642


--
Sawan Gupta
sawangupta.it@GMail.com
http://www.SawanSoft.com
(+91)9829124642

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

RE: VB6 Problem

Can you send the piece of code when the error occurs?

=20

Saludos,

=20

Carlos Olivas Barba

Gerente de sistemas

Mayan Sea Garden

Mazatl=E1n, Sinaloa.


-----Mensaje original-----
De: Sawan Gupta [mailto:sawangupta.it@gmail.com]=20
Enviado el: Viernes, 30 de Diciembre de 2005 06:55 p.m.
Para: myodbc@lists.mysql.com
Asunto: RE: VB6 Problem

Yes I have the MDAC 2.8 installed. I also ran WIndows Update and
system is fully updated with all patches.

What else should I check?

Thanks a lot.

Warm Regards,



On 12/28/05, Lu=EDs Damas wrote:
> Check if you have the last MDAC instaled (2.8)
> www.microsoft.com/data
>
>
> Regards
> Luis Damas
> ----- Original Message -----
> From: "Sawan Gupta"
> To:
> Sent: Wednesday, December 28, 2005 12:23 PM
> Subject: VB6 Problem
>
>
> I had developed a VB6 application on my Win XP SP2 machine. Later my
> HDD crashed and I have lost the source code.
>
>
> I dont remember which version of MyODBC I was using. My mysql version
> was mysql-4.0.18-win.
>
> My application now gives me the following errors on windows xp sp2
>
> run time error 383
> text property is read only
>
> Run time error '3705'
> operation is not allowed when the object is open.
>
> How do I eliminate these errors. I tried various older version of
> MyODBC too but didnt got any sucess.
>
> Thanks a lot.
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:
http://lists.mysql.com/myodbc?unsub=3Dsamad@mail.telepac.pt
>
>
>
>


--
Sawan Gupta
sawangupta.it@GMail.com
http://www.SawanSoft.com
(+91)9829124642


--
Sawan Gupta
sawangupta.it@GMail.com
http://www.SawanSoft.com
(+91)9829124642

--=20
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=3Dcarlosolivas@seagarden .com.mx


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

Re: VB6 Problem

I dont have the source code, My Hard disk got crashed. I am just left
with the executable which use to run fine earlier but now doesn't.

Regards,

Sawan Gupta


On 1/5/06, Carlos Olivas Barba wrote:
> Can you send the piece of code when the error occurs?
>
>
>
> Saludos,
>
>
>
> Carlos Olivas Barba
>
> Gerente de sistemas
>
> Mayan Sea Garden
>
> Mazatl=E1n, Sinaloa.
>
>
> -----Mensaje original-----
> De: Sawan Gupta [mailto:sawangupta.it@gmail.com]
> Enviado el: Viernes, 30 de Diciembre de 2005 06:55 p.m.
> Para: myodbc@lists.mysql.com
> Asunto: RE: VB6 Problem
>
> Yes I have the MDAC 2.8 installed. I also ran WIndows Update and
> system is fully updated with all patches.
>
> What else should I check?
>
> Thanks a lot.
>
> Warm Regards,
>
>
>
> On 12/28/05, Lu=EDs Damas wrote:
> > Check if you have the last MDAC instaled (2.8)
> > www.microsoft.com/data
> >
> >
> > Regards
> > Luis Damas
> > ----- Original Message -----
> > From: "Sawan Gupta"
> > To:
> > Sent: Wednesday, December 28, 2005 12:23 PM
> > Subject: VB6 Problem
> >
> >
> > I had developed a VB6 application on my Win XP SP2 machine. Later my
> > HDD crashed and I have lost the source code.
> >
> >
> > I dont remember which version of MyODBC I was using. My mysql version
> > was mysql-4.0.18-win.
> >
> > My application now gives me the following errors on windows xp sp2
> >
> > run time error 383
> > text property is read only
> >
> > Run time error '3705'
> > operation is not allowed when the object is open.
> >
> > How do I eliminate these errors. I tried various older version of
> > MyODBC too but didnt got any sucess.
> >
> > Thanks a lot.

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

AW: VB6 Problem

Hi there,

Sawan, let me give you a opinion about the 383 error message:

If you have a combobox, style 2 - dropdown list, and you try to set this
list to a value which is not included to the list then you will receive =
a
383. For example: You got a dropdown combo style 2 - dropdown list, and =
you
fill it with dates (e.g. 01.01.2006, 02.01.2006, 03.01.2006, 04.01.2006) =
and
later in the code you try to set it to a 05.01.2006 you will receive =
this
message, because 05.01.2006 is not a value of the list.=20

So in your case, the 383 may happen because you have to resetup your
computer. In the old computer you got maybe special settings for the =
date
format? Now you didnt set this values again (because you forgot about =
it),
but the vb6 code is waiting for this format to select something from the
combo box. Maybe you have system date format "dd/m/yyyy" but you fill =
the
combobox like shown above (dd.mm.yyyy). When you now try to set a date =
it
will fail.=20

This is about where the 383 comes from, and I personaly think that the =
383
has nothing to do with the 3705 which comes a bit later. I think you got =
2
problems there.

Hope this helps a bit
Michael


-----Ursprüngliche Nachricht-----
Von: Sawan Gupta [mailto:sawangupta.it@gmail.com]=20
Gesendet: Donnerstag, 05. Jänner 2006 03:07
An: myodbc@lists.mysql.com
Betreff: Re: VB6 Problem


I dont have the source code, My Hard disk got crashed. I am just left =
with
the executable which use to run fine earlier but now doesn't.

Regards,

Sawan Gupta


On 1/5/06, Carlos Olivas Barba wrote:
> Can you send the piece of code when the error occurs?
>
>
>
> Saludos,
>
>
>
> Carlos Olivas Barba
>
> Gerente de sistemas
>
> Mayan Sea Garden
>
> Mazatl=E1n, Sinaloa.
>
>
> -----Mensaje original-----
> De: Sawan Gupta [mailto:sawangupta.it@gmail.com]
> Enviado el: Viernes, 30 de Diciembre de 2005 06:55 p.m.
> Para: myodbc@lists.mysql.com
> Asunto: RE: VB6 Problem
>
> Yes I have the MDAC 2.8 installed. I also ran WIndows Update and=20
> system is fully updated with all patches.
>
> What else should I check?
>
> Thanks a lot.
>
> Warm Regards,
>
>
>
> On 12/28/05, Lu=EDs Damas wrote:
> > Check if you have the last MDAC instaled (2.8)=20
> > www.microsoft.com/data
> >
> >
> > Regards
> > Luis Damas
> > ----- Original Message -----
> > From: "Sawan Gupta"
> > To:
> > Sent: Wednesday, December 28, 2005 12:23 PM
> > Subject: VB6 Problem
> >
> >
> > I had developed a VB6 application on my Win XP SP2 machine. Later my =

> > HDD crashed and I have lost the source code.
> >
> >
> > I dont remember which version of MyODBC I was using. My mysql=20
> > version was mysql-4.0.18-win.
> >
> > My application now gives me the following errors on windows xp sp2
> >
> > run time error 383
> > text property is read only
> >
> > Run time error '3705'
> > operation is not allowed when the object is open.
> >
> > How do I eliminate these errors. I tried various older version of=20
> > MyODBC too but didnt got any sucess.
> >
> > Thanks a lot.

--=20
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=3Dmichael.haunzwickl@syn .at



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

Re: VB6 Problem

Thanx a lot, it worked. Could you please suggest something for the error 37=
05.

Thanx again.


Sawan


On 1/5/06, Michael Haunzwickl / SYN wrote:
> Hi there,
>
> Sawan, let me give you a opinion about the 383 error message:
>
> If you have a combobox, style 2 - dropdown list, and you try to set this
> list to a value which is not included to the list then you will receive a
> 383. For example: You got a dropdown combo style 2 - dropdown list, and y=
ou
> fill it with dates (e.g. 01.01.2006, 02.01.2006, 03.01.2006, 04.01.2006) =
and
> later in the code you try to set it to a 05.01.2006 you will receive this
> message, because 05.01.2006 is not a value of the list.
>
> So in your case, the 383 may happen because you have to resetup your
> computer. In the old computer you got maybe special settings for the date
> format? Now you didnt set this values again (because you forgot about it)=
,
> but the vb6 code is waiting for this format to select something from the
> combo box. Maybe you have system date format "dd/m/yyyy" but you fill the
> combobox like shown above (dd.mm.yyyy). When you now try to set a date it
> will fail.
>
> This is about where the 383 comes from, and I personaly think that the 38=
3
> has nothing to do with the 3705 which comes a bit later. I think you got =
2
> problems there.
>
> Hope this helps a bit
> Michael
>
>
> -----Ursprüngliche Nachricht-----
> Von: Sawan Gupta [mailto:sawangupta.it@gmail.com]
> Gesendet: Donnerstag, 05. Jänner 2006 03:07
> An: myodbc@lists.mysql.com
> Betreff: Re: VB6 Problem
>
>
> I dont have the source code, My Hard disk got crashed. I am just left wit=
h
> the executable which use to run fine earlier but now doesn't.
>
> Regards,
>
> Sawan Gupta
>
>
> On 1/5/06, Carlos Olivas Barba wrote:
> > Can you send the piece of code when the error occurs?
> >
> >
> >
> > Saludos,
> >
> >
> >
> > Carlos Olivas Barba
> >
> > Gerente de sistemas
> >
> > Mayan Sea Garden
> >
> > Mazatl=E1n, Sinaloa.
> >
> >
> > -----Mensaje original-----
> > De: Sawan Gupta [mailto:sawangupta.it@gmail.com]
> > Enviado el: Viernes, 30 de Diciembre de 2005 06:55 p.m.
> > Para: myodbc@lists.mysql.com
> > Asunto: RE: VB6 Problem
> >
> > Yes I have the MDAC 2.8 installed. I also ran WIndows Update and
> > system is fully updated with all patches.
> >
> > What else should I check?
> >
> > Thanks a lot.
> >
> > Warm Regards,
> >
> >
> >
> > On 12/28/05, Lu=EDs Damas wrote:
> > > Check if you have the last MDAC instaled (2.8)
> > > www.microsoft.com/data
> > >
> > >
> > > Regards
> > > Luis Damas
> > > ----- Original Message -----
> > > From: "Sawan Gupta"
> > > To:
> > > Sent: Wednesday, December 28, 2005 12:23 PM
> > > Subject: VB6 Problem
> > >
> > >
> > > I had developed a VB6 application on my Win XP SP2 machine. Later my
> > > HDD crashed and I have lost the source code.
> > >
> > >
> > > I dont remember which version of MyODBC I was using. My mysql
> > > version was mysql-4.0.18-win.
> > >
> > > My application now gives me the following errors on windows xp sp2
> > >
> > > run time error 383
> > > text property is read only
> > >
> > > Run time error '3705'
> > > operation is not allowed when the object is open.
> > >
> > > How do I eliminate these errors. I tried various older version of
> > > MyODBC too but didnt got any sucess.
> > >
> > > Thanks a lot.
>
>

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

AW: VB6 Problem

Well, it's fine to hear it works.

Lets see what the 3705 can bee. According to the MSDN it means:

"Operation is not allowed when the object is open. An object that is =
open
cannot be opened. Fields cannot be appended to an open Recordset."

That means, if you have a recordset "rs", it is open, and you try to =
open it
again without closing it before. Same problem appear if rs is open and =
you
try to release rs with "set rs =3D nothing" (while it is open) ... This =
will
also end in this error. So, it means you are trying to do anything with =
an
OPEN recordset, which is only allowed to a closed one.=20

The question which still stay is: Why/how did it work before?=20

Is it possible that you have error fetching in your module? See the
following example:

On Error GoTo HANDLE_ERROR

Dim conn As ADODB.Connection
Dim rs As ADODB.Recordset
Dim varZeile As Integer
=20
Set conn =3D New ADODB.Connection
Set rs =3D New ADODB.Recordset
conn.CursorLocation =3D adUseClient
conn.ConnectionString =3D varConnectionString
conn.Open
=20
=20
varSQLCommand =3D "select zonenname from tzoneneinteilungen where
zonenname is not null group by zonenname"
rs.Open varSQLCommand, conn, adOpenStatic, adLockOptimistic,
adCmdText
If rs.RecordCount <> 0 Then
rs.MoveFirst
Do Until rs.EOF
=20
' Here we are in a loop
x
x
x
x
' Here occours ANY error ... So the procedure jumps to
"HANDLE_ERROR"
x
x
x
=09
rs.MoveNext
Loop

End If
rs.Close
conn.Close
=20
Set rs =3D Nothing
Set conn =3D Nothing
=20
=20
=20
Exit Sub
Hadle_error:
If Err <> 94 Then

varSQLCommand =3D "select * from terror_table where 1=3D0"
rs.Open varSQLCommand, conn, adOpenStatic, adLockOptimistic,
adCmdText
If rs.RecordCount <> 0 Then
' *** bla bla bla=09
endif

End If
Resume Next


You can see, i am openening "RS" here to get some data from a table. =
Because
i am wating for more then 1 record i will run into a loop to do =
something
with the data. In the middle of the loop i will run into ANY error =
(doesnt
metter which one). I got a error procedure which will put the errors =
into a
table so that i can trace it. BUT: in the error procedure =
(handle_error:) I
am trying to open the recordset "RS" which is allready open from the =
first
part of the module. This will end in a 3705.

What does it mean for you? It means that it may happen that the error is
basicly another one, but because the error handler is generating a newer
one, you will see this one.=20

Are you sure you got an actual copy of the database? (all fields in the
tables)?

What else can you try? Did you to set the odbc tracing on? This may help =
you
see where the error comes from. It will rapidly slow down the =
application
.... But it will maybe help you see where the error happens.

Michael



-----Ursprüngliche Nachricht-----
Von: Sawan Gupta [mailto:sawangupta.it@gmail.com]=20
Gesendet: Freitag, 06. Jänner 2006 11:19
An: myodbc@lists.mysql.com
Betreff: Re: VB6 Problem


Thanx a lot, it worked. Could you please suggest something for the error
3705.

Thanx again.


Sawan


On 1/5/06, Michael Haunzwickl / SYN wrote:
> Hi there,
>
> Sawan, let me give you a opinion about the 383 error message:
>
> If you have a combobox, style 2 - dropdown list, and you try to set=20
> this list to a value which is not included to the list then you will=20
> receive a 383. For example: You got a dropdown combo style 2 -=20
> dropdown list, and you fill it with dates (e.g. 01.01.2006,=20
> 02.01.2006, 03.01.2006, 04.01.2006) and later in the code you try to=20
> set it to a 05.01.2006 you will receive this message, because=20
> 05.01.2006 is not a value of the list.
>
> So in your case, the 383 may happen because you have to resetup your=20
> computer. In the old computer you got maybe special settings for the=20
> date format? Now you didnt set this values again (because you forgot=20
> about it), but the vb6 code is waiting for this format to select=20
> something from the combo box. Maybe you have system date format=20
> "dd/m/yyyy" but you fill the combobox like shown above (dd.mm.yyyy).=20
> When you now try to set a date it will fail.
>
> This is about where the 383 comes from, and I personaly think that the =

> 383 has nothing to do with the 3705 which comes a bit later. I think=20
> you got 2 problems there.
>
> Hope this helps a bit
> Michael
>
>
> -----Ursprüngliche Nachricht-----
> Von: Sawan Gupta [mailto:sawangupta.it@gmail.com]
> Gesendet: Donnerstag, 05. Jänner 2006 03:07
> An: myodbc@lists.mysql.com
> Betreff: Re: VB6 Problem
>
>
> I dont have the source code, My Hard disk got crashed. I am just left=20
> with the executable which use to run fine earlier but now doesn't.
>
> Regards,
>
> Sawan Gupta
>
>
> On 1/5/06, Carlos Olivas Barba wrote:
> > Can you send the piece of code when the error occurs?
> >
> >
> >
> > Saludos,
> >
> >
> >
> > Carlos Olivas Barba
> >
> > Gerente de sistemas
> >
> > Mayan Sea Garden
> >
> > Mazatl=E1n, Sinaloa.
> >
> >
> > -----Mensaje original-----
> > De: Sawan Gupta [mailto:sawangupta.it@gmail.com]
> > Enviado el: Viernes, 30 de Diciembre de 2005 06:55 p.m.
> > Para: myodbc@lists.mysql.com
> > Asunto: RE: VB6 Problem
> >
> > Yes I have the MDAC 2.8 installed. I also ran WIndows Update and=20
> > system is fully updated with all patches.
> >
> > What else should I check?
> >
> > Thanks a lot.
> >
> > Warm Regards,
> >
> >
> >
> > On 12/28/05, Lu=EDs Damas wrote:
> > > Check if you have the last MDAC instaled (2.8)=20
> > > www.microsoft.com/data
> > >
> > >
> > > Regards
> > > Luis Damas
> > > ----- Original Message -----
> > > From: "Sawan Gupta"
> > > To:
> > > Sent: Wednesday, December 28, 2005 12:23 PM
> > > Subject: VB6 Problem
> > >
> > >
> > > I had developed a VB6 application on my Win XP SP2 machine. Later=20
> > > my HDD crashed and I have lost the source code.
> > >
> > >
> > > I dont remember which version of MyODBC I was using. My mysql=20
> > > version was mysql-4.0.18-win.
> > >
> > > My application now gives me the following errors on windows xp sp2
> > >
> > > run time error 383
> > > text property is read only
> > >
> > > Run time error '3705'
> > > operation is not allowed when the object is open.
> > >
> > > How do I eliminate these errors. I tried various older version of=20
> > > MyODBC too but didnt got any sucess.
> > >
> > > Thanks a lot.
>
>

--=20
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:
http://lists.mysql.com/myodbc?unsub=3Dmichael.haunzwickl@syn .at


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg