Read-only Error On Addnew

I'm new to MySQL so my problem is probably pretty elementary. I'm using
ODBC and VB6 to access a database in the MySQL server I've set up. The
application is running on the same computer. My problem is that when
attempting to add a record to a table (recordset), I get an error saying
that the database is read-only. The code snippet included (below my
signature) seems to be the same as the example in the reference manual =
(ODBC
section) but I consistently get a 3027 error. I presume that this is a
configuration error on my part but I've been unable to find out what I'm
doing wrong.

This occurs with the root UID and password.

Any suggestions?

Thanks in advance for whatever help you can offer.



=20

Lawson Cronlund
Voice Response Technologies, Inc.
5717 E. Justine Rd.
Scottsdale, AZ 85254

lawson@vrtinc.com
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)
=20


========== Error from run time =
====================

-----------------------------------------------------
| |
| |
| Run-time error '3027': |
| |
| Cannot update. Database or object is read-only. |
| |
| |
-----------------------------------------------------

============ code snippet =
==================
****** Module level declarations *****
Dim wkTest As Workspace
Dim dbTest As Connection
Dim rsTest As Recordset
Dim ODBCStr As String
Dim SQL As String

****** Form/Load code *********
Set wkTest =3D CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
ODBCStr =3D "ODBC;" & _
"DSN=3DIVRCallRecords;" & _
"UID=3Droot;PWD=3Dxxxxxxxx; OPTION=3D3;"
Set dbTest =3D wkTest.OpenConnection("ivrcallrecords", _
dbDriverNoPrompt, _
False, _
ODBCStr)
SQL =3D "SELECT * FROM logcallstarts;"
Set rsTest =3D dbTest.OpenRecordset _
(SQL _
, dbOpenDynaset, 0, dbOptimistic)
' , dbOpenDynaset, 0, dbPessimistic)
rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
rsTest.Fields![StartDTG] =3D Now
rsTest.Update
..
..
..
=================3D end code snippet =
===============3D


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

RE: Read-only Error On Addnew

Thank you for the suggestion.

I checked and although the directory/folder for the "ivrcallrecords"
database was marked with read-only, the individual tables in the directory
were not. I changed the directory/folder to reset the read-only attribute
but that didn't make any difference.

When I use a commercially available MySQL graphical client (Navicat) I can
access the tables and modify them. However, this client does not use ODBC
so my problem probably has something to do with the ODBC settings. As far
as I can tell, I've set the ODBC options the same way that the mysql
database is configured. So far all my variations on settings have always
resulted in the same result of an error 3027 (read-only database).

Any help is appreciated.

Thank you all.



Lawson Cronlund
lawson@vrtinc.com
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)


-----Original Message-----
From: Van Sederburg [mailto:vps@onepost.net]
Sent: Wednesday, November 09, 2005 11:25 AM
To: lawson@vrtinc.com
Subject: Re: Read-only Error On Addnew


Make sure the database files themselves are not marked as read only in the
file system.

i.e., go to [mysql dir]/data/yourdatabase/

Select all files, right click, choose Properties, and clear the Read Only
checkbox.

This typically happens if the database files are moved via CD-Rom or some
other read only media.

Van


> I'm new to MySQL so my problem is probably pretty elementary. I'm using
> ODBC and VB6 to access a database in the MySQL server I've set up. The
> application is running on the same computer. My problem is that when
> attempting to add a record to a table (recordset), I get an error saying
> that the database is read-only. The code snippet included (below my
> signature) seems to be the same as the example in the reference manual
> (ODBC
> section) but I consistently get a 3027 error. I presume that this is a
> configuration error on my part but I've been unable to find out what I'm
> doing wrong.
>
> This occurs with the root UID and password.
>
> Any suggestions?
>
> Thanks in advance for whatever help you can offer.
>
>
>
>
>
> Lawson Cronlund
> Voice Response Technologies, Inc.
> 5717 E. Justine Rd.
> Scottsdale, AZ 85254
>
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>
>
>
> ========== Error from run time ====================
>
> -----------------------------------------------------
> | |
> | |
> | Run-time error '3027': |
> | |
> | Cannot update. Database or object is read-only. |
> | |
> | |
> -----------------------------------------------------
>
> ============ code snippet ==================
> ****** Module level declarations *****
> Dim wkTest As Workspace
> Dim dbTest As Connection
> Dim rsTest As Recordset
> Dim ODBCStr As String
> Dim SQL As String
>
> ****** Form/Load code *********
> Set wkTest = CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
> ODBCStr = "ODBC;" & _
> "DSN=IVRCallRecords;" & _
> "UID=root;PWD=xxxxxxxx; OPTION=3;"
> Set dbTest = wkTest.OpenConnection("ivrcallrecords", _
> dbDriverNoPrompt, _
> False, _
> ODBCStr)
> SQL = "SELECT * FROM logcallstarts;"
> Set rsTest = dbTest.OpenRecordset _
> (SQL _
> , dbOpenDynaset, 0, dbOptimistic)
> ' , dbOpenDynaset, 0, dbPessimistic)
> rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
> rsTest.Fields![StartDTG] = Now
> rsTest.Update
> .
> .
> .
> ================= end code snippet ===============
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=vps@onepost.net
>
>
>



--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

RE: Read-only Error On Addnew

I have not been able to get the AddNew method to work in VB6 using ODBC
3.51.12 or 3.51.12-2 in conjunction with MySQL 5.0.15 (generally available)
running on WinXP. Every configuration that I've tried so far has resulted
in an error 3027 being reported or a problem report being sent back to
Microsoft for a serious failure.

Does anyone know if this is a known problem or is it a configuration issue
in how I've set up the ODBC definition?

If someone has the above configuration working, could you let me know what
configuration items I need to set in the ODBC definition.

Do I need to drop back to an earlier version of MySQL due to some
incompatibility between Win XP, MySQL 5.0.15, and ODBC 3.51.12?

Thanks in advance for any help offered.



Lawson Cronlund
lawson@vrtinc.com
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)


-----Original Message-----
From: Lawson Cronlund [mailto:lawson@vrtinc.com]
Sent: Wednesday, November 09, 2005 12:50 PM
To: vps@onepost.net; 'MySQL Win32 List'
Subject: RE: Read-only Error On Addnew


Thank you for the suggestion.

I checked and although the directory/folder for the "ivrcallrecords"
database was marked with read-only, the individual tables in the directory
were not. I changed the directory/folder to reset the read-only attribute
but that didn't make any difference.

When I use a commercially available MySQL graphical client (Navicat) I can
access the tables and modify them. However, this client does not use ODBC
so my problem probably has something to do with the ODBC settings. As far
as I can tell, I've set the ODBC options the same way that the mysql
database is configured. So far all my variations on settings have always
resulted in the same result of an error 3027 (read-only database).

Any help is appreciated.

Thank you all.



Lawson Cronlund
lawson@vrtinc.com
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)


-----Original Message-----
From: Van Sederburg [mailto:vps@onepost.net]
Sent: Wednesday, November 09, 2005 11:25 AM
To: lawson@vrtinc.com
Subject: Re: Read-only Error On Addnew


Make sure the database files themselves are not marked as read only in the
file system.

i.e., go to [mysql dir]/data/yourdatabase/

Select all files, right click, choose Properties, and clear the Read Only
checkbox.

This typically happens if the database files are moved via CD-Rom or some
other read only media.

Van


> I'm new to MySQL so my problem is probably pretty elementary. I'm using
> ODBC and VB6 to access a database in the MySQL server I've set up. The
> application is running on the same computer. My problem is that when
> attempting to add a record to a table (recordset), I get an error saying
> that the database is read-only. The code snippet included (below my
> signature) seems to be the same as the example in the reference manual
> (ODBC
> section) but I consistently get a 3027 error. I presume that this is a
> configuration error on my part but I've been unable to find out what I'm
> doing wrong.
>
> This occurs with the root UID and password.
>
> Any suggestions?
>
> Thanks in advance for whatever help you can offer.
>
>
>
>
>
> Lawson Cronlund
> Voice Response Technologies, Inc.
> 5717 E. Justine Rd.
> Scottsdale, AZ 85254
>
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>
>
>
> ========== Error from run time ====================
>
> -----------------------------------------------------
> | |
> | |
> | Run-time error '3027': |
> | |
> | Cannot update. Database or object is read-only. |
> | |
> | |
> -----------------------------------------------------
>
> ============ code snippet ==================
> ****** Module level declarations *****
> Dim wkTest As Workspace
> Dim dbTest As Connection
> Dim rsTest As Recordset
> Dim ODBCStr As String
> Dim SQL As String
>
> ****** Form/Load code *********
> Set wkTest = CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
> ODBCStr = "ODBC;" & _
> "DSN=IVRCallRecords;" & _
> "UID=root;PWD=xxxxxxxx; OPTION=3;"
> Set dbTest = wkTest.OpenConnection("ivrcallrecords", _
> dbDriverNoPrompt, _
> False, _
> ODBCStr)
> SQL = "SELECT * FROM logcallstarts;"
> Set rsTest = dbTest.OpenRecordset _
> (SQL _
> , dbOpenDynaset, 0, dbOptimistic)
> ' , dbOpenDynaset, 0, dbPessimistic)
> rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
> rsTest.Fields![StartDTG] = Now
> rsTest.Update
> .
> .
> .
> ================= end code snippet ===============
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=vps@onepost.net
>
>
>



--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=lawson@vrtinc.com


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

RE: Read-only Error On Addnew

--=_alternative 0052791C852570B5_=
Content-Type: text/plain; charset="US-ASCII"

It may be related to this

http://lists.mysql.com/mysql/190524
http://lists.mysql.com/mysql/190529 (same thread, just not linked to it in
the archive)

- or this -

There is some reason that Access needs a particular MySQL table setup in
order to work with it as a linked table without throwing a bunch of
#deleted# values into its display every time you change or add a record.
Follow the directions for hooking Access into MySQL and your program
should work just fine as I believe Access also uses the .AddNew method to
do several things.

General info: http://dev.mysql.com/doc/refman/5.0/en/odbc-connector.html
MyODBC vs. Access: http://dev.mysql.com/doc/refman/5.0/en/msaccess.html
MyODBC vs. VBA and ASP: http://dev.mysql.com/doc/refman/5.0/en/msvba.html

Sorry I can't be more specific. Please share what works and what didn't.

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine


"Lawson Cronlund" wrote on 11/10/2005 03:56:29 AM:

> I have not been able to get the AddNew method to work in VB6 using ODBC
> 3.51.12 or 3.51.12-2 in conjunction with MySQL 5.0.15 (generally
available)
> running on WinXP. Every configuration that I've tried so far has
resulted
> in an error 3027 being reported or a problem report being sent back to
> Microsoft for a serious failure.
>
> Does anyone know if this is a known problem or is it a configuration
issue
> in how I've set up the ODBC definition?
>
> If someone has the above configuration working, could you let me know
what
> configuration items I need to set in the ODBC definition.
>
> Do I need to drop back to an earlier version of MySQL due to some
> incompatibility between Win XP, MySQL 5.0.15, and ODBC 3.51.12?
>
> Thanks in advance for any help offered.
>
>
>
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>
>
> -----Original Message-----
> From: Lawson Cronlund [mailto:lawson@vrtinc.com]
> Sent: Wednesday, November 09, 2005 12:50 PM
> To: vps@onepost.net; 'MySQL Win32 List'
> Subject: RE: Read-only Error On Addnew
>
>
> Thank you for the suggestion.
>
> I checked and although the directory/folder for the "ivrcallrecords"
> database was marked with read-only, the individual tables in the
directory
> were not. I changed the directory/folder to reset the read-only
attribute
> but that didn't make any difference.
>
> When I use a commercially available MySQL graphical client (Navicat) I
can
> access the tables and modify them. However, this client does not use
ODBC
> so my problem probably has something to do with the ODBC settings. As
far
> as I can tell, I've set the ODBC options the same way that the mysql
> database is configured. So far all my variations on settings have
always
> resulted in the same result of an error 3027 (read-only database).
>
> Any help is appreciated.
>
> Thank you all.
>
>
>
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>
>
> -----Original Message-----
> From: Van Sederburg [mailto:vps@onepost.net]
> Sent: Wednesday, November 09, 2005 11:25 AM
> To: lawson@vrtinc.com
> Subject: Re: Read-only Error On Addnew
>
>
> Make sure the database files themselves are not marked as read only in
the
> file system.
>
> i.e., go to [mysql dir]/data/yourdatabase/
>
> Select all files, right click, choose Properties, and clear the Read
Only
> checkbox.
>
> This typically happens if the database files are moved via CD-Rom or
some
> other read only media.
>
> Van
>
>
> > I'm new to MySQL so my problem is probably pretty elementary. I'm
using
> > ODBC and VB6 to access a database in the MySQL server I've set up. The
> > application is running on the same computer. My problem is that when
> > attempting to add a record to a table (recordset), I get an error
saying
> > that the database is read-only. The code snippet included (below my
> > signature) seems to be the same as the example in the reference manual
> > (ODBC
> > section) but I consistently get a 3027 error. I presume that this is
a
> > configuration error on my part but I've been unable to find out what
I'm
> > doing wrong.
> >
> > This occurs with the root UID and password.
> >
> > Any suggestions?
> >
> > Thanks in advance for whatever help you can offer.
> >
> >
> >
> >
> >
> > Lawson Cronlund
> > Voice Response Technologies, Inc.
> > 5717 E. Justine Rd.
> > Scottsdale, AZ 85254
> >
> > lawson@vrtinc.com
> > +1(480)308-0641 (Voice)
> > +1(602)996-0376 (Fax)
> >
> >
> >
> > ========== Error from run time ====================
> >
> > -----------------------------------------------------
> > | |
> > | |
> > | Run-time error '3027': |
> > | |
> > | Cannot update. Database or object is read-only. |
> > | |
> > | |
> > -----------------------------------------------------
> >
> > ============ code snippet ==================
> > ****** Module level declarations *****
> > Dim wkTest As Workspace
> > Dim dbTest As Connection
> > Dim rsTest As Recordset
> > Dim ODBCStr As String
> > Dim SQL As String
> >
> > ****** Form/Load code *********
> > Set wkTest = CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
> > ODBCStr = "ODBC;" & _
> > "DSN=IVRCallRecords;" & _
> > "UID=root;PWD=xxxxxxxx; OPTION=3;"
> > Set dbTest = wkTest.OpenConnection("ivrcallrecords", _
> > dbDriverNoPrompt, _
> > False, _
> > ODBCStr)
> > SQL = "SELECT * FROM logcallstarts;"
> > Set rsTest = dbTest.OpenRecordset _
> > (SQL _
> > , dbOpenDynaset, 0, dbOptimistic)
> > ' , dbOpenDynaset, 0, dbPessimistic)
> > rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
> > rsTest.Fields![StartDTG] = Now
> > rsTest.Update
> > .
> > .
> > .
> > ================= end code snippet ===============
> >
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe: http://lists.mysql.com/win32?unsub=vps@onepost.net
> >
> >
> >
>
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=lawson@vrtinc.com
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=sgreen@unimin.com
>

--=_alternative 0052791C852570B5_=--

RE: Read-only Error On Addnew

Shawn,

Thank you for the suggestion. I tried following the 5 steps in the
directions in the referenced section (24.1.11.1).

1. Apply MDAC 2.6 or above and apply MSJet4.0 SP5. Windows XP =
Professional
includes the data access components so the MDAC package refuses to =
install.
The SP reported for the jet engine is 8. I went ahead and tried to =
apply
the SP5 reference anyway. This section was written for older versions =
of
MySQL and MyODBC since it references what I suspect is a pretty old =
versions
of both.

2. Use latest version of MySQL. I'm working with MySQL 5.0.15 (latest =
GA
release).

3. Use 3.51 or 2.5 version or later of MyODBC. I've tried using both
3.51.12 and 3.51.12-2 with the same results.

4. Enable the "Return Matching Rows" option. This is set in the ODBC
configuration. I think that the OPTION=3D3; setting in the connection =
string
sets this as one of its bit mapped configuration items. But I also set =
it
in the graphical ODBC DAN name configuration.

5. Start working with Access.

The end result of this was that I could no longer establish a connection =
to
the database so it appears that a step back was taken.

My conclusion at this point is that there is a compatibility issue with
Windows XP Pro (latest patch and service pack updates) and MyODBC for =
the
versions I've tested (3.51.12 and 3.51.12-2). It appears that the MySQL
engine is compatible with Windows XP Pro because the non-ODBC client =
that I
bought and am using for diagnosis and administration works just fine =
either
from the local computer or from a remote computer.

It's not worth pursuing this unless someone at MySQL identifies this as =
a
configuration issue on my part. My forehead is pretty flat from this =
one
now and there're no holes in the brick wall.

Can you suggest a direct connection client (e.g. OCX/DLL) that would =
allow
me to incorporate an SQL interface into my VB6 application without going
through ODBC?

Thanks for your help.



Lawson Cronlund
lawson@vrtinc.com
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)
=20

-----Original Message-----
From: SGreen@unimin.com [mailto:SGreen@unimin.com]=20
Sent: Thursday, November 10, 2005 8:01 AM
To: lawson@vrtinc.com
Cc: 'MySQL Win32 List'
Subject: RE: Read-only Error On Addnew


It may be related to this

http://lists.mysql.com/mysql/190524
http://lists.mysql.com/mysql/190529 (same thread, just not linked to it =
in=20
the archive)

- or this -=20

There is some reason that Access needs a particular MySQL table setup =
in=20
order to work with it as a linked table without throwing a bunch of=20
#deleted# values into its display every time you change or add a record. =

Follow the directions for hooking Access into MySQL and your program=20
should work just fine as I believe Access also uses the .AddNew method =
to=20
do several things.

General info: http://dev.mysql.com/doc/refman/5.0/en/odbc-connector.html
MyODBC vs. Access: http://dev.mysql.com/doc/refman/5.0/en/msaccess.html
MyODBC vs. VBA and ASP: =
http://dev.mysql.com/doc/refman/5.0/en/msvba.html

Sorry I can't be more specific. Please share what works and what didn't.

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine


"Lawson Cronlund" wrote on 11/10/2005 03:56:29 AM:

> I have not been able to get the AddNew method to work in VB6 using =
ODBC
> 3.51.12 or 3.51.12-2 in conjunction with MySQL 5.0.15 (generally=20
available)
> running on WinXP. Every configuration that I've tried so far has=20
resulted
> in an error 3027 being reported or a problem report being sent back to
> Microsoft for a serious failure.
>=20
> Does anyone know if this is a known problem or is it a configuration=20
issue
> in how I've set up the ODBC definition?
>=20
> If someone has the above configuration working, could you let me know=20
what
> configuration items I need to set in the ODBC definition.=20
>=20
> Do I need to drop back to an earlier version of MySQL due to some
> incompatibility between Win XP, MySQL 5.0.15, and ODBC 3.51.12?
>=20
> Thanks in advance for any help offered.
>=20
>=20
>=20
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>=20
>=20
> -----Original Message-----
> From: Lawson Cronlund [mailto:lawson@vrtinc.com]=20
> Sent: Wednesday, November 09, 2005 12:50 PM
> To: vps@onepost.net; 'MySQL Win32 List'
> Subject: RE: Read-only Error On Addnew
>=20
>=20
> Thank you for the suggestion.
>=20
> I checked and although the directory/folder for the "ivrcallrecords"
> database was marked with read-only, the individual tables in the=20
directory
> were not. I changed the directory/folder to reset the read-only=20
attribute
> but that didn't make any difference.
>=20
> When I use a commercially available MySQL graphical client (Navicat) I =

can
> access the tables and modify them. However, this client does not use=20
ODBC
> so my problem probably has something to do with the ODBC settings. As =

far
> as I can tell, I've set the ODBC options the same way that the mysql
> database is configured. So far all my variations on settings have=20
always
> resulted in the same result of an error 3027 (read-only database).
>=20
> Any help is appreciated.
>=20
> Thank you all.
>=20
>=20
>=20
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>=20
>=20
> -----Original Message-----
> From: Van Sederburg [mailto:vps@onepost.net]=20
> Sent: Wednesday, November 09, 2005 11:25 AM
> To: lawson@vrtinc.com
> Subject: Re: Read-only Error On Addnew
>=20
>=20
> Make sure the database files themselves are not marked as read only in =

the
> file system.
>=20
> i.e., go to [mysql dir]/data/yourdatabase/
>=20
> Select all files, right click, choose Properties, and clear the Read=20
Only
> checkbox.
>=20
> This typically happens if the database files are moved via CD-Rom or=20
some
> other read only media.
>=20
> Van
>=20
>=20
> > I'm new to MySQL so my problem is probably pretty elementary. I'm=20
using
> > ODBC and VB6 to access a database in the MySQL server I've set up. =
The
> > application is running on the same computer. My problem is that =
when
> > attempting to add a record to a table (recordset), I get an error=20
saying
> > that the database is read-only. The code snippet included (below my
> > signature) seems to be the same as the example in the reference =
manual
> > (ODBC
> > section) but I consistently get a 3027 error. I presume that this =
is=20
a
> > configuration error on my part but I've been unable to find out what =

I'm
> > doing wrong.
> >
> > This occurs with the root UID and password.
> >
> > Any suggestions?
> >
> > Thanks in advance for whatever help you can offer.
> >
> >
> >
> >
> >
> > Lawson Cronlund
> > Voice Response Technologies, Inc.
> > 5717 E. Justine Rd.
> > Scottsdale, AZ 85254
> >
> > lawson@vrtinc.com
> > +1(480)308-0641 (Voice)
> > +1(602)996-0376 (Fax)
> >
> >
> >
> > ========== Error from run time =
====================
> >
> > -----------------------------------------------------
> > | |
> > | |
> > | Run-time error '3027': |
> > | |
> > | Cannot update. Database or object is read-only. |
> > | |
> > | |
> > -----------------------------------------------------
> >
> > ============ code snippet =
==================
> > ****** Module level declarations *****
> > Dim wkTest As Workspace
> > Dim dbTest As Connection
> > Dim rsTest As Recordset
> > Dim ODBCStr As String
> > Dim SQL As String
> >
> > ****** Form/Load code *********
> > Set wkTest =3D CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
> > ODBCStr =3D "ODBC;" & _
> > "DSN=3DIVRCallRecords;" & _
> > "UID=3Droot;PWD=3Dxxxxxxxx; OPTION=3D3;"
> > Set dbTest =3D wkTest.OpenConnection("ivrcallrecords", _
> > dbDriverNoPrompt, _
> > False, _
> > ODBCStr)
> > SQL =3D "SELECT * FROM logcallstarts;"
> > Set rsTest =3D dbTest.OpenRecordset _
> > (SQL _
> > , dbOpenDynaset, 0, dbOptimistic)
> > ' , dbOpenDynaset, 0, dbPessimistic)
> > rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
> > rsTest.Fields![StartDTG] =3D Now
> > rsTest.Update
> > .
> > .
> > .
> > =================3D end code snippet =
===============3D
> >
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe: =
http://lists.mysql.com/win32?unsub=3Dvps@onepost.net
> >
> >
> >
>=20
>=20
>=20
> --=20
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: =
http://lists.mysql.com/win32?unsub=3Dlawson@vrtinc.com
>=20
>=20
> --=20
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: =
http://lists.mysql.com/win32?unsub=3Dsgreen@unimin.com
>=20


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

RE: Read-only Error On Addnew

Kevin,

I had not realized that about ODBC. However, I have the Primary Key =
defined
for an AutoNumber field in each table in my test configuration (good
discipline as a general rule).

You might see my conclusions about this in another posting to the list =
that
I just sent. Basically, I've come to the conclusion that the MyODBC =
driver
is incompatible with Window XP Pro. If I'm wrong, I'm sure that I'll
receive comments from the list community.

If you have any suggestions as to an OCX or DLL that I could use from my =
VB6
application that would allow me to get recordset functionality in the
program without going through the ODBC driver, please let me know.

Thanks for your help.



Lawson Cronlund
lawson@vrtinc.com
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)
=20

-----Original Message-----
From: Kevin Rutledge [mailto:kevin@in-genius.com]=20
Sent: Thursday, November 10, 2005 8:06 AM
To: lawson@vrtinc.com
Subject: RE: Read-only Error On Addnew


ODBC will not add records to tables without a primary key defined.

> -----Original Message-----
> From: Lawson Cronlund [mailto:lawson@vrtinc.com]=20
> Sent: Wednesday, November 09, 2005 11:50 AM
> To: vps@onepost.net; MySQL Win32 List
> Subject: RE: Read-only Error On Addnew
>=20
> Thank you for the suggestion.
>=20
> I checked and although the directory/folder for the "ivrcallrecords"
> database was marked with read-only, the individual tables in=20
> the directory
> were not. I changed the directory/folder to reset the=20
> read-only attribute
> but that didn't make any difference.
>=20
> When I use a commercially available MySQL graphical client=20
> (Navicat) I can
> access the tables and modify them. However, this client does=20
> not use ODBC
> so my problem probably has something to do with the ODBC=20
> settings. As far
> as I can tell, I've set the ODBC options the same way that the mysql
> database is configured. So far all my variations on settings=20
> have always
> resulted in the same result of an error 3027 (read-only database).
>=20
> Any help is appreciated.
>=20
> Thank you all.
>=20
>=20
>=20
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
> =20
>=20
> -----Original Message-----
> From: Van Sederburg [mailto:vps@onepost.net]=20
> Sent: Wednesday, November 09, 2005 11:25 AM
> To: lawson@vrtinc.com
> Subject: Re: Read-only Error On Addnew
>=20
>=20
> Make sure the database files themselves are not marked as=20
> read only in the
> file system.
>=20
> i.e., go to [mysql dir]/data/yourdatabase/
>=20
> Select all files, right click, choose Properties, and clear=20
> the Read Only
> checkbox.
>=20
> This typically happens if the database files are moved via=20
> CD-Rom or some
> other read only media.
>=20
> Van
>=20
>=20
> > I'm new to MySQL so my problem is probably pretty=20
> elementary. I'm using
> > ODBC and VB6 to access a database in the MySQL server I've=20
> set up. The
> > application is running on the same computer. My problem is=20
> that when
> > attempting to add a record to a table (recordset), I get an=20
> error saying
> > that the database is read-only. The code snippet included (below my
> > signature) seems to be the same as the example in the=20
> reference manual
> > (ODBC
> > section) but I consistently get a 3027 error. I presume=20
> that this is a
> > configuration error on my part but I've been unable to find=20
> out what I'm
> > doing wrong.
> >
> > This occurs with the root UID and password.
> >
> > Any suggestions?
> >
> > Thanks in advance for whatever help you can offer.
> >
> >
> >
> >
> >
> > Lawson Cronlund
> > Voice Response Technologies, Inc.
> > 5717 E. Justine Rd.
> > Scottsdale, AZ 85254
> >
> > lawson@vrtinc.com
> > +1(480)308-0641 (Voice)
> > +1(602)996-0376 (Fax)
> >
> >
> >
> > ========== Error from run time =
====================
> >
> > -----------------------------------------------------
> > | |
> > | |
> > | Run-time error '3027': |
> > | |
> > | Cannot update. Database or object is read-only. |
> > | |
> > | |
> > -----------------------------------------------------
> >
> > ============ code snippet =
==================
> > ****** Module level declarations *****
> > Dim wkTest As Workspace
> > Dim dbTest As Connection
> > Dim rsTest As Recordset
> > Dim ODBCStr As String
> > Dim SQL As String
> >
> > ****** Form/Load code *********
> > Set wkTest =3D CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
> > ODBCStr =3D "ODBC;" & _
> > "DSN=3DIVRCallRecords;" & _
> > "UID=3Droot;PWD=3Dxxxxxxxx; OPTION=3D3;"
> > Set dbTest =3D wkTest.OpenConnection("ivrcallrecords", _
> > dbDriverNoPrompt, _
> > False, _
> > ODBCStr)
> > SQL =3D "SELECT * FROM logcallstarts;"
> > Set rsTest =3D dbTest.OpenRecordset _
> > (SQL _
> > , dbOpenDynaset, 0, dbOptimistic)
> > ' , dbOpenDynaset, 0, dbPessimistic)
> > rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
> > rsTest.Fields![StartDTG] =3D Now
> > rsTest.Update
> > .
> > .
> > .
> > =================3D end code snippet =
===============3D
> >
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe: =20
> http://lists.mysql.com/win32?unsub=3Dvps@onepost.net
> >
> >
> >
>=20
>=20
>=20
> --=20
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: =20
> http://lists.mysql.com/win32?unsub=3Dml.mysql@in-genius.com
>=20


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

RE: Read-only Error On Addnew

--=_alternative 001F5AF1852570B6_=
Content-Type: text/plain; charset="US-ASCII"

The mysql server ships with libmysqld.dll and libmysql.dll. The C-API uses
these two dlls for it's interace. You could alias the appropriate C-style
functions (see the MSDN examples for using the Win32 library from VB on
how to alias a c-style funcation in VB).There are other project that
create connectors from different languages to MySQL (.NET, PHP, and Java
jump to mind) so there is probably one for VB as well.

http://dev.mysql.com/doc/refman/4.1/en/apis.html

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine



"Lawson Cronlund" wrote on 11/11/2005 12:02:36 AM:

> Shawn,
>
> Thank you for the suggestion. I tried following the 5 steps in the
> directions in the referenced section (24.1.11.1).
>
> 1. Apply MDAC 2.6 or above and apply MSJet4.0 SP5. Windows XP
Professional
> includes the data access components so the MDAC package refuses to
install.
> The SP reported for the jet engine is 8. I went ahead and tried to
apply
> the SP5 reference anyway. This section was written for older versions
of
> MySQL and MyODBC since it references what I suspect is a pretty old
versions
> of both.
>
> 2. Use latest version of MySQL. I'm working with MySQL 5.0.15 (latest
GA
> release).
>
> 3. Use 3.51 or 2.5 version or later of MyODBC. I've tried using both
> 3.51.12 and 3.51.12-2 with the same results.
>
> 4. Enable the "Return Matching Rows" option. This is set in the ODBC
> configuration. I think that the OPTION=3; setting in the connection
string
> sets this as one of its bit mapped configuration items. But I also set
it
> in the graphical ODBC DAN name configuration.
>
> 5. Start working with Access.
>
> The end result of this was that I could no longer establish a connection
to
> the database so it appears that a step back was taken.
>
> My conclusion at this point is that there is a compatibility issue with
> Windows XP Pro (latest patch and service pack updates) and MyODBC for
the
> versions I've tested (3.51.12 and 3.51.12-2). It appears that the MySQL
> engine is compatible with Windows XP Pro because the non-ODBC client
that I
> bought and am using for diagnosis and administration works just fine
either
> from the local computer or from a remote computer.
>
> It's not worth pursuing this unless someone at MySQL identifies this as
a
> configuration issue on my part. My forehead is pretty flat from this
one
> now and there're no holes in the brick wall.
>
> Can you suggest a direct connection client (e.g. OCX/DLL) that would
allow
> me to incorporate an SQL interface into my VB6 application without going
> through ODBC?
>
> Thanks for your help.
>
>
>
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>
>
> -----Original Message-----
> From: SGreen@unimin.com [mailto:SGreen@unimin.com]
> Sent: Thursday, November 10, 2005 8:01 AM
> To: lawson@vrtinc.com
> Cc: 'MySQL Win32 List'
> Subject: RE: Read-only Error On Addnew
>
>
> It may be related to this
>
> http://lists.mysql.com/mysql/190524
> http://lists.mysql.com/mysql/190529 (same thread, just not linked to it
in
> the archive)
>
> - or this -
>
> There is some reason that Access needs a particular MySQL table setup
in
> order to work with it as a linked table without throwing a bunch of
> #deleted# values into its display every time you change or add a record.

> Follow the directions for hooking Access into MySQL and your program
> should work just fine as I believe Access also uses the .AddNew method
to
> do several things.
>
> General info: http://dev.mysql.com/doc/refman/5.0/en/odbc-connector.html
> MyODBC vs. Access: http://dev.mysql.com/doc/refman/5.0/en/msaccess.html
> MyODBC vs. VBA and ASP:
http://dev.mysql.com/doc/refman/5.0/en/msvba.html
>
> Sorry I can't be more specific. Please share what works and what didn't.
>
> Shawn Green
> Database Administrator
> Unimin Corporation - Spruce Pine
>
>
> "Lawson Cronlund" wrote on 11/10/2005 03:56:29 AM:
>
> > I have not been able to get the AddNew method to work in VB6 using
ODBC
> > 3.51.12 or 3.51.12-2 in conjunction with MySQL 5.0.15 (generally
> available)
> > running on WinXP. Every configuration that I've tried so far has
> resulted
> > in an error 3027 being reported or a problem report being sent back to
> > Microsoft for a serious failure.
> >
> > Does anyone know if this is a known problem or is it a configuration
> issue
> > in how I've set up the ODBC definition?
> >
> > If someone has the above configuration working, could you let me know
> what
> > configuration items I need to set in the ODBC definition.
> >
> > Do I need to drop back to an earlier version of MySQL due to some
> > incompatibility between Win XP, MySQL 5.0.15, and ODBC 3.51.12?
> >
> > Thanks in advance for any help offered.
> >
> >
> >
> > Lawson Cronlund
> > lawson@vrtinc.com
> > +1(480)308-0641 (Voice)
> > +1(602)996-0376 (Fax)
> >
> >
> > -----Original Message-----
> > From: Lawson Cronlund [mailto:lawson@vrtinc.com]
> > Sent: Wednesday, November 09, 2005 12:50 PM
> > To: vps@onepost.net; 'MySQL Win32 List'
> > Subject: RE: Read-only Error On Addnew
> >
> >
> > Thank you for the suggestion.
> >
> > I checked and although the directory/folder for the "ivrcallrecords"
> > database was marked with read-only, the individual tables in the
> directory
> > were not. I changed the directory/folder to reset the read-only
> attribute
> > but that didn't make any difference.
> >
> > When I use a commercially available MySQL graphical client (Navicat) I

> can
> > access the tables and modify them. However, this client does not use
> ODBC
> > so my problem probably has something to do with the ODBC settings. As

> far
> > as I can tell, I've set the ODBC options the same way that the mysql
> > database is configured. So far all my variations on settings have
> always
> > resulted in the same result of an error 3027 (read-only database).
> >
> > Any help is appreciated.
> >
> > Thank you all.
> >
> >
> >
> > Lawson Cronlund
> > lawson@vrtinc.com
> > +1(480)308-0641 (Voice)
> > +1(602)996-0376 (Fax)
> >
> >
> > -----Original Message-----
> > From: Van Sederburg [mailto:vps@onepost.net]
> > Sent: Wednesday, November 09, 2005 11:25 AM
> > To: lawson@vrtinc.com
> > Subject: Re: Read-only Error On Addnew
> >
> >
> > Make sure the database files themselves are not marked as read only in

> the
> > file system.
> >
> > i.e., go to [mysql dir]/data/yourdatabase/
> >
> > Select all files, right click, choose Properties, and clear the Read
> Only
> > checkbox.
> >
> > This typically happens if the database files are moved via CD-Rom or
> some
> > other read only media.
> >
> > Van
> >
> >
> > > I'm new to MySQL so my problem is probably pretty elementary. I'm
> using
> > > ODBC and VB6 to access a database in the MySQL server I've set up.
The
> > > application is running on the same computer. My problem is that
when
> > > attempting to add a record to a table (recordset), I get an error
> saying
> > > that the database is read-only. The code snippet included (below my
> > > signature) seems to be the same as the example in the reference
manual
> > > (ODBC
> > > section) but I consistently get a 3027 error. I presume that this
is
> a
> > > configuration error on my part but I've been unable to find out what

> I'm
> > > doing wrong.
> > >
> > > This occurs with the root UID and password.
> > >
> > > Any suggestions?
> > >
> > > Thanks in advance for whatever help you can offer.
> > >
> > >
> > >
> > >
> > >
> > > Lawson Cronlund
> > > Voice Response Technologies, Inc.
> > > 5717 E. Justine Rd.
> > > Scottsdale, AZ 85254
> > >
> > > lawson@vrtinc.com
> > > +1(480)308-0641 (Voice)
> > > +1(602)996-0376 (Fax)
> > >
> > >
> > >
> > > ========== Error from run time ====================
> > >
> > > -----------------------------------------------------
> > > | |
> > > | |
> > > | Run-time error '3027': |
> > > | |
> > > | Cannot update. Database or object is read-only. |
> > > | |
> > > | |
> > > -----------------------------------------------------
> > >
> > > ============ code snippet ==================
> > > ****** Module level declarations *****
> > > Dim wkTest As Workspace
> > > Dim dbTest As Connection
> > > Dim rsTest As Recordset
> > > Dim ODBCStr As String
> > > Dim SQL As String
> > >
> > > ****** Form/Load code *********
> > > Set wkTest = CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
> > > ODBCStr = "ODBC;" & _
> > > "DSN=IVRCallRecords;" & _
> > > "UID=root;PWD=xxxxxxxx; OPTION=3;"
> > > Set dbTest = wkTest.OpenConnection("ivrcallrecords", _
> > > dbDriverNoPrompt, _
> > > False, _
> > > ODBCStr)
> > > SQL = "SELECT * FROM logcallstarts;"
> > > Set rsTest = dbTest.OpenRecordset _
> > > (SQL _
> > > , dbOpenDynaset, 0, dbOptimistic)
> > > ' , dbOpenDynaset, 0, dbPessimistic)
> > > rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
> > > rsTest.Fields![StartDTG] = Now
> > > rsTest.Update
> > > .
> > > .
> > > .
> > > ================= end code snippet ===============
> > >
> > >
> > > --
> > > MySQL Windows Mailing List
> > > For list archives: http://lists.mysql.com/win32
> > > To unsubscribe: http://lists.mysql.com/win32?unsub=vps@onepost.net
> > >
> > >
> > >
> >
> >
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe: http://lists.mysql.com/win32?unsub=lawson@vrtinc.com
> >
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe: http://lists.mysql.com/win32?unsub=sgreen@unimin.com
> >
>

--=_alternative 001F5AF1852570B6_=--

RE: Read-only Error On Addnew

Try this http://www.vbmysql.com/projects/vbmysqldirect/

This is what I use with VB6. Don't seem to have any problems. I am
running XP Pro too and it works with various versions of MySQL.

The calls are similar to what you would use with ADODB. Get back to me
if you need any examples.

John B.

-----Original Message-----
From: Lawson Cronlund [mailto:lawson@vrtinc.com]=20
Sent: Friday, 11 November 2005 3:33 PM
To: SGreen@unimin.com; 'MySQL Win32 List'
Subject: RE: Read-only Error On Addnew

Shawn,

Thank you for the suggestion. I tried following the 5 steps in the
directions in the referenced section (24.1.11.1).

1. Apply MDAC 2.6 or above and apply MSJet4.0 SP5. Windows XP
Professional
includes the data access components so the MDAC package refuses to
install.
The SP reported for the jet engine is 8. I went ahead and tried to
apply
the SP5 reference anyway. This section was written for older versions
of
MySQL and MyODBC since it references what I suspect is a pretty old
versions
of both.

2. Use latest version of MySQL. I'm working with MySQL 5.0.15 (latest
GA
release).

3. Use 3.51 or 2.5 version or later of MyODBC. I've tried using both
3.51.12 and 3.51.12-2 with the same results.

4. Enable the "Return Matching Rows" option. This is set in the ODBC
configuration. I think that the OPTION=3D3; setting in the connection
string
sets this as one of its bit mapped configuration items. But I also set
it
in the graphical ODBC DAN name configuration.

5. Start working with Access.

The end result of this was that I could no longer establish a connection
to
the database so it appears that a step back was taken.

My conclusion at this point is that there is a compatibility issue with
Windows XP Pro (latest patch and service pack updates) and MyODBC for
the
versions I've tested (3.51.12 and 3.51.12-2). It appears that the MySQL
engine is compatible with Windows XP Pro because the non-ODBC client
that I
bought and am using for diagnosis and administration works just fine
either
from the local computer or from a remote computer.

It's not worth pursuing this unless someone at MySQL identifies this as
a
configuration issue on my part. My forehead is pretty flat from this
one
now and there're no holes in the brick wall.

Can you suggest a direct connection client (e.g. OCX/DLL) that would
allow
me to incorporate an SQL interface into my VB6 application without going
through ODBC?

Thanks for your help.



Lawson Cronlund
lawson@vrtinc.com
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)
=20

-----Original Message-----
From: SGreen@unimin.com [mailto:SGreen@unimin.com]=20
Sent: Thursday, November 10, 2005 8:01 AM
To: lawson@vrtinc.com
Cc: 'MySQL Win32 List'
Subject: RE: Read-only Error On Addnew


It may be related to this

http://lists.mysql.com/mysql/190524
http://lists.mysql.com/mysql/190529 (same thread, just not linked to it
in=20
the archive)

- or this -=20

There is some reason that Access needs a particular MySQL table setup
in=20
order to work with it as a linked table without throwing a bunch of=20
#deleted# values into its display every time you change or add a record.

Follow the directions for hooking Access into MySQL and your program=20
should work just fine as I believe Access also uses the .AddNew method
to=20
do several things.

General info: http://dev.mysql.com/doc/refman/5.0/en/odbc-connector.html
MyODBC vs. Access: http://dev.mysql.com/doc/refman/5.0/en/msaccess.html
MyODBC vs. VBA and ASP:
http://dev.mysql.com/doc/refman/5.0/en/msvba.html

Sorry I can't be more specific. Please share what works and what didn't.

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine


"Lawson Cronlund" wrote on 11/10/2005 03:56:29 AM:

> I have not been able to get the AddNew method to work in VB6 using
ODBC
> 3.51.12 or 3.51.12-2 in conjunction with MySQL 5.0.15 (generally=20
available)
> running on WinXP. Every configuration that I've tried so far has=20
resulted
> in an error 3027 being reported or a problem report being sent back to
> Microsoft for a serious failure.
>=20
> Does anyone know if this is a known problem or is it a configuration=20
issue
> in how I've set up the ODBC definition?
>=20
> If someone has the above configuration working, could you let me know=20
what
> configuration items I need to set in the ODBC definition.=20
>=20
> Do I need to drop back to an earlier version of MySQL due to some
> incompatibility between Win XP, MySQL 5.0.15, and ODBC 3.51.12?
>=20
> Thanks in advance for any help offered.
>=20
>=20
>=20
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>=20
>=20
> -----Original Message-----
> From: Lawson Cronlund [mailto:lawson@vrtinc.com]=20
> Sent: Wednesday, November 09, 2005 12:50 PM
> To: vps@onepost.net; 'MySQL Win32 List'
> Subject: RE: Read-only Error On Addnew
>=20
>=20
> Thank you for the suggestion.
>=20
> I checked and although the directory/folder for the "ivrcallrecords"
> database was marked with read-only, the individual tables in the=20
directory
> were not. I changed the directory/folder to reset the read-only=20
attribute
> but that didn't make any difference.
>=20
> When I use a commercially available MySQL graphical client (Navicat) I

can
> access the tables and modify them. However, this client does not use=20
ODBC
> so my problem probably has something to do with the ODBC settings. As

far
> as I can tell, I've set the ODBC options the same way that the mysql
> database is configured. So far all my variations on settings have=20
always
> resulted in the same result of an error 3027 (read-only database).
>=20
> Any help is appreciated.
>=20
> Thank you all.
>=20
>=20
>=20
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>=20
>=20
> -----Original Message-----
> From: Van Sederburg [mailto:vps@onepost.net]=20
> Sent: Wednesday, November 09, 2005 11:25 AM
> To: lawson@vrtinc.com
> Subject: Re: Read-only Error On Addnew
>=20
>=20
> Make sure the database files themselves are not marked as read only in

the
> file system.
>=20
> i.e., go to [mysql dir]/data/yourdatabase/
>=20
> Select all files, right click, choose Properties, and clear the Read=20
Only
> checkbox.
>=20
> This typically happens if the database files are moved via CD-Rom or=20
some
> other read only media.
>=20
> Van
>=20
>=20
> > I'm new to MySQL so my problem is probably pretty elementary. I'm=20
using
> > ODBC and VB6 to access a database in the MySQL server I've set up.
The
> > application is running on the same computer. My problem is that
when
> > attempting to add a record to a table (recordset), I get an error=20
saying
> > that the database is read-only. The code snippet included (below my
> > signature) seems to be the same as the example in the reference
manual
> > (ODBC
> > section) but I consistently get a 3027 error. I presume that this
is=20
a
> > configuration error on my part but I've been unable to find out what

I'm
> > doing wrong.
> >
> > This occurs with the root UID and password.
> >
> > Any suggestions?
> >
> > Thanks in advance for whatever help you can offer.
> >
> >
> >
> >
> >
> > Lawson Cronlund
> > Voice Response Technologies, Inc.
> > 5717 E. Justine Rd.
> > Scottsdale, AZ 85254
> >
> > lawson@vrtinc.com
> > +1(480)308-0641 (Voice)
> > +1(602)996-0376 (Fax)
> >
> >
> >
> > ========== Error from run time =
====================
> >
> > -----------------------------------------------------
> > | |
> > | |
> > | Run-time error '3027': |
> > | |
> > | Cannot update. Database or object is read-only. |
> > | |
> > | |
> > -----------------------------------------------------
> >
> > ============ code snippet =
==================
> > ****** Module level declarations *****
> > Dim wkTest As Workspace
> > Dim dbTest As Connection
> > Dim rsTest As Recordset
> > Dim ODBCStr As String
> > Dim SQL As String
> >
> > ****** Form/Load code *********
> > Set wkTest =3D CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
> > ODBCStr =3D "ODBC;" & _
> > "DSN=3DIVRCallRecords;" & _
> > "UID=3Droot;PWD=3Dxxxxxxxx; OPTION=3D3;"
> > Set dbTest =3D wkTest.OpenConnection("ivrcallrecords", _
> > dbDriverNoPrompt, _
> > False, _
> > ODBCStr)
> > SQL =3D "SELECT * FROM logcallstarts;"
> > Set rsTest =3D dbTest.OpenRecordset _
> > (SQL _
> > , dbOpenDynaset, 0, dbOptimistic)
> > ' , dbOpenDynaset, 0, dbPessimistic)
> > rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
> > rsTest.Fields![StartDTG] =3D Now
> > rsTest.Update
> > .
> > .
> > .
> > =================3D end code snippet =
===============3D
> >
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe:
http://lists.mysql.com/win32?unsub=3Dvps@onepost.net
> >
> >
> >
>=20
>=20
>=20
> --=20
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
http://lists.mysql.com/win32?unsub=3Dlawson@vrtinc.com
>=20
>=20
> --=20
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
http://lists.mysql.com/win32?unsub=3Dsgreen@unimin.com
>=20



--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

RE: Read-only Error On Addnew

John B.,

I appreciate your giving me the reference to the VBMySQLDirect project.

That provides a technical solution to my problem. It appears that my
assumption that MyODBC is not compatible with XP is correct (or I don't =
know
the proper configuration).

My preferred approach is now to use the VBMySQLDirect approach. I have =
to
evaluate:

1. The implications of using logic (the .DLL) identified as alpha in a
customer environment - even though the date of the last change in the =
change
log is 3/28/2004.

2. My understanding that I can have the VBMySQLDirect .dll installed on =
a
computer and then used by a proprietary application without placing the
proprietary application under the GPL. This will require that I read =
the
LGPL carefully to verify my understanding.

3. The probability that the MyODBC package will be brought up to XP
compatibility in the future for the DAO access that is currently in the
application (to keep the generality).

4. The probability of abandonment of the VBMySQLDirect approach. There =
is
no activity indicated on the package for about 1.5 years now.

Once again, thank you for the information. I very much appreciate =
this.

Regards.





Lawson
lawson@vrtinc.com
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)
=20

-----Original Message-----
From: jbonnett@sola.com.au [mailto:jbonnett@sola.com.au]=20
Sent: Sunday, November 13, 2005 3:14 PM
To: lawson@vrtinc.com; SGreen@unimin.com; win32@lists.mysql.com
Subject: RE: Read-only Error On Addnew


Try this http://www.vbmysql.com/projects/vbmysqldirect/

This is what I use with VB6. Don't seem to have any problems. I am
running XP Pro too and it works with various versions of MySQL.

The calls are similar to what you would use with ADODB. Get back to me
if you need any examples.

John B.

-----Original Message-----
From: Lawson Cronlund [mailto:lawson@vrtinc.com]=20
Sent: Friday, 11 November 2005 3:33 PM
To: SGreen@unimin.com; 'MySQL Win32 List'
Subject: RE: Read-only Error On Addnew

Shawn,

Thank you for the suggestion. I tried following the 5 steps in the
directions in the referenced section (24.1.11.1).

1. Apply MDAC 2.6 or above and apply MSJet4.0 SP5. Windows XP
Professional
includes the data access components so the MDAC package refuses to
install.
The SP reported for the jet engine is 8. I went ahead and tried to
apply
the SP5 reference anyway. This section was written for older versions
of
MySQL and MyODBC since it references what I suspect is a pretty old
versions
of both.

2. Use latest version of MySQL. I'm working with MySQL 5.0.15 (latest
GA
release).

3. Use 3.51 or 2.5 version or later of MyODBC. I've tried using both
3.51.12 and 3.51.12-2 with the same results.

4. Enable the "Return Matching Rows" option. This is set in the ODBC
configuration. I think that the OPTION=3D3; setting in the connection
string
sets this as one of its bit mapped configuration items. But I also set
it
in the graphical ODBC DAN name configuration.

5. Start working with Access.

The end result of this was that I could no longer establish a connection
to
the database so it appears that a step back was taken.

My conclusion at this point is that there is a compatibility issue with
Windows XP Pro (latest patch and service pack updates) and MyODBC for
the
versions I've tested (3.51.12 and 3.51.12-2). It appears that the MySQL
engine is compatible with Windows XP Pro because the non-ODBC client
that I
bought and am using for diagnosis and administration works just fine
either
from the local computer or from a remote computer.

It's not worth pursuing this unless someone at MySQL identifies this as
a
configuration issue on my part. My forehead is pretty flat from this
one
now and there're no holes in the brick wall.

Can you suggest a direct connection client (e.g. OCX/DLL) that would
allow
me to incorporate an SQL interface into my VB6 application without going
through ODBC?

Thanks for your help.



Lawson Cronlund
lawson@vrtinc.com
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)
=20

-----Original Message-----
From: SGreen@unimin.com [mailto:SGreen@unimin.com]=20
Sent: Thursday, November 10, 2005 8:01 AM
To: lawson@vrtinc.com
Cc: 'MySQL Win32 List'
Subject: RE: Read-only Error On Addnew


It may be related to this

http://lists.mysql.com/mysql/190524
http://lists.mysql.com/mysql/190529 (same thread, just not linked to it
in=20
the archive)

- or this -=20

There is some reason that Access needs a particular MySQL table setup
in=20
order to work with it as a linked table without throwing a bunch of=20
#deleted# values into its display every time you change or add a record.

Follow the directions for hooking Access into MySQL and your program=20
should work just fine as I believe Access also uses the .AddNew method
to=20
do several things.

General info: http://dev.mysql.com/doc/refman/5.0/en/odbc-connector.html
MyODBC vs. Access: http://dev.mysql.com/doc/refman/5.0/en/msaccess.html
MyODBC vs. VBA and ASP:
http://dev.mysql.com/doc/refman/5.0/en/msvba.html

Sorry I can't be more specific. Please share what works and what didn't.

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine


"Lawson Cronlund" wrote on 11/10/2005 03:56:29 AM:

> I have not been able to get the AddNew method to work in VB6 using
ODBC
> 3.51.12 or 3.51.12-2 in conjunction with MySQL 5.0.15 (generally=20
available)
> running on WinXP. Every configuration that I've tried so far has=20
resulted
> in an error 3027 being reported or a problem report being sent back to
> Microsoft for a serious failure.
>=20
> Does anyone know if this is a known problem or is it a configuration=20
issue
> in how I've set up the ODBC definition?
>=20
> If someone has the above configuration working, could you let me know=20
what
> configuration items I need to set in the ODBC definition.=20
>=20
> Do I need to drop back to an earlier version of MySQL due to some
> incompatibility between Win XP, MySQL 5.0.15, and ODBC 3.51.12?
>=20
> Thanks in advance for any help offered.
>=20
>=20
>=20
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>=20
>=20
> -----Original Message-----
> From: Lawson Cronlund [mailto:lawson@vrtinc.com]=20
> Sent: Wednesday, November 09, 2005 12:50 PM
> To: vps@onepost.net; 'MySQL Win32 List'
> Subject: RE: Read-only Error On Addnew
>=20
>=20
> Thank you for the suggestion.
>=20
> I checked and although the directory/folder for the "ivrcallrecords"
> database was marked with read-only, the individual tables in the=20
directory
> were not. I changed the directory/folder to reset the read-only=20
attribute
> but that didn't make any difference.
>=20
> When I use a commercially available MySQL graphical client (Navicat) I

can
> access the tables and modify them. However, this client does not use=20
ODBC
> so my problem probably has something to do with the ODBC settings. As

far
> as I can tell, I've set the ODBC options the same way that the mysql
> database is configured. So far all my variations on settings have=20
always
> resulted in the same result of an error 3027 (read-only database).
>=20
> Any help is appreciated.
>=20
> Thank you all.
>=20
>=20
>=20
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>=20
>=20
> -----Original Message-----
> From: Van Sederburg [mailto:vps@onepost.net]=20
> Sent: Wednesday, November 09, 2005 11:25 AM
> To: lawson@vrtinc.com
> Subject: Re: Read-only Error On Addnew
>=20
>=20
> Make sure the database files themselves are not marked as read only in

the
> file system.
>=20
> i.e., go to [mysql dir]/data/yourdatabase/
>=20
> Select all files, right click, choose Properties, and clear the Read=20
Only
> checkbox.
>=20
> This typically happens if the database files are moved via CD-Rom or=20
some
> other read only media.
>=20
> Van
>=20
>=20
> > I'm new to MySQL so my problem is probably pretty elementary. I'm=20
using
> > ODBC and VB6 to access a database in the MySQL server I've set up.
The
> > application is running on the same computer. My problem is that
when
> > attempting to add a record to a table (recordset), I get an error=20
saying
> > that the database is read-only. The code snippet included (below my
> > signature) seems to be the same as the example in the reference
manual
> > (ODBC
> > section) but I consistently get a 3027 error. I presume that this
is=20
a
> > configuration error on my part but I've been unable to find out what

I'm
> > doing wrong.
> >
> > This occurs with the root UID and password.
> >
> > Any suggestions?
> >
> > Thanks in advance for whatever help you can offer.
> >
> >
> >
> >
> >
> > Lawson Cronlund
> > Voice Response Technologies, Inc.
> > 5717 E. Justine Rd.
> > Scottsdale, AZ 85254
> >
> > lawson@vrtinc.com
> > +1(480)308-0641 (Voice)
> > +1(602)996-0376 (Fax)
> >
> >
> >
> > ========== Error from run time =
====================
> >
> > -----------------------------------------------------
> > | |
> > | |
> > | Run-time error '3027': |
> > | |
> > | Cannot update. Database or object is read-only. |
> > | |
> > | |
> > -----------------------------------------------------
> >
> > ============ code snippet =
==================
> > ****** Module level declarations *****
> > Dim wkTest As Workspace
> > Dim dbTest As Connection
> > Dim rsTest As Recordset
> > Dim ODBCStr As String
> > Dim SQL As String
> >
> > ****** Form/Load code *********
> > Set wkTest =3D CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
> > ODBCStr =3D "ODBC;" & _
> > "DSN=3DIVRCallRecords;" & _
> > "UID=3Droot;PWD=3Dxxxxxxxx; OPTION=3D3;"
> > Set dbTest =3D wkTest.OpenConnection("ivrcallrecords", _
> > dbDriverNoPrompt, _
> > False, _
> > ODBCStr)
> > SQL =3D "SELECT * FROM logcallstarts;"
> > Set rsTest =3D dbTest.OpenRecordset _
> > (SQL _
> > , dbOpenDynaset, 0, dbOptimistic)
> > ' , dbOpenDynaset, 0, dbPessimistic)
> > rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
> > rsTest.Fields![StartDTG] =3D Now
> > rsTest.Update
> > .
> > .
> > .
> > =================3D end code snippet =
===============3D
> >
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe:
http://lists.mysql.com/win32?unsub=3Dvps@onepost.net
> >
> >
> >
>=20
>=20
>=20
> --=20
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
http://lists.mysql.com/win32?unsub=3Dlawson@vrtinc.com
>=20
>=20
> --=20
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
http://lists.mysql.com/win32?unsub=3Dsgreen@unimin.com
>=20



--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

Re: Read-only Error On Addnew

On 11/14/05, Lawson Cronlund wrote:
> John B.,
>
> I appreciate your giving me the reference to the VBMySQLDirect project.

That's what I'm using with VBA to let Word access MySQL and deal with data.

> That provides a technical solution to my problem. It appears that my
> assumption that MyODBC is not compatible with XP is correct (or I don't k=
now
> the proper configuration).

Probably configuration, I used ODBC, but dropped it because I was too
lazy to develop an installer that would attach and install MyODBC,
along with problems using DSNs. Anyway, it was my choice and I never
regret it... :) Installing the VBMYSQLDirect.dll was piece of cake
with Nullsoft installer, so, I followed the easiest path.

> My preferred approach is now to use the VBMySQLDirect approach. I have t=
o
> evaluate:
>
> 1. The implications of using logic (the .DLL) identified as alpha in a
> customer environment - even though the date of the last change in the cha=
nge
> log is 3/28/2004.

Never had problems beside the fact that the user that connect needs an
OLD_PASSWORD format in order to work correctly, dunno why, don't care.
Shouldn't be necessary as the last version was already 4.1 when the
library was linked, but well, who cares again?!

> 2. My understanding that I can have the VBMySQLDirect .dll installed on =
a
> computer and then used by a proprietary application without placing the
> proprietary application under the GPL. This will require that I read the
> LGPL carefully to verify my understanding.

LGPL is special, you'll have to read it and understand it to use, but
understand that it applies to the LIBRARY, that's not an app, at least
not a complete one, so, I guess you won't turn your app into GPL just
by using it, you can contact the FSF to get more info about it (I've
found the docs in LGPL that come with VBMySQLDirect kinda confuse.

> 3. The probability that the MyODBC package will be brought up to XP
> compatibility in the future for the DAO access that is currently in the
> application (to keep the generality).

Well, you'll have to deal with it, but if you keep your app clean and
modules easy to update, you won't have problems abstracting the use of
VBMySQLDirect, using new set of objects that connects, writes, reads
or change data and closes the connection using methods of the object
YOU created, this way, when/if you change to MyODBC, you'll have a few
if any problem (just changing the object you created to use ODBC
instead of VBMySQLDirect).

> 4. The probability of abandonment of the VBMySQLDirect approach. There =
is
> no activity indicated on the package for about 1.5 years now.

Well, the library is used just to connect, issue queries and deal with
a few errors, nothing too big, you can issue any querie, so, creating
and using stored procedures and other new approaches won't affect you
much as you'll only send and receive data, I've been using this
library with many versions of MySQL and never had issues.

> Once again, thank you for the information. I very much appreciate this.
>
> Regards.
>
>
>
>
>
> Lawson
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>
>
> -----Original Message-----
> From: jbonnett@sola.com.au [mailto:jbonnett@sola.com.au]
> Sent: Sunday, November 13, 2005 3:14 PM
> To: lawson@vrtinc.com; SGreen@unimin.com; win32@lists.mysql.com
> Subject: RE: Read-only Error On Addnew
>
>
> Try this http://www.vbmysql.com/projects/vbmysqldirect/
>
> This is what I use with VB6. Don't seem to have any problems. I am
> running XP Pro too and it works with various versions of MySQL.
>
> The calls are similar to what you would use with ADODB. Get back to me
> if you need any examples.
>
> John B.
>
> -----Original Message-----
> From: Lawson Cronlund [mailto:lawson@vrtinc.com]
> Sent: Friday, 11 November 2005 3:33 PM
> To: SGreen@unimin.com; 'MySQL Win32 List'
> Subject: RE: Read-only Error On Addnew
>
> Shawn,
>
> Thank you for the suggestion. I tried following the 5 steps in the
> directions in the referenced section (24.1.11.1).
>
> 1. Apply MDAC 2.6 or above and apply MSJet4.0 SP5. Windows XP
> Professional
> includes the data access components so the MDAC package refuses to
> install.
> The SP reported for the jet engine is 8. I went ahead and tried to
> apply
> the SP5 reference anyway. This section was written for older versions
> of
> MySQL and MyODBC since it references what I suspect is a pretty old
> versions
> of both.
>
> 2. Use latest version of MySQL. I'm working with MySQL 5.0.15 (latest
> GA
> release).
>
> 3. Use 3.51 or 2.5 version or later of MyODBC. I've tried using both
> 3.51.12 and 3.51.12-2 with the same results.
>
> 4. Enable the "Return Matching Rows" option. This is set in the ODBC
> configuration. I think that the OPTION=3D3; setting in the connection
> string
> sets this as one of its bit mapped configuration items. But I also set
> it
> in the graphical ODBC DAN name configuration.
>
> 5. Start working with Access.
>
> The end result of this was that I could no longer establish a connection
> to
> the database so it appears that a step back was taken.
>
> My conclusion at this point is that there is a compatibility issue with
> Windows XP Pro (latest patch and service pack updates) and MyODBC for
> the
> versions I've tested (3.51.12 and 3.51.12-2). It appears that the MySQL
> engine is compatible with Windows XP Pro because the non-ODBC client
> that I
> bought and am using for diagnosis and administration works just fine
> either
> from the local computer or from a remote computer.
>
> It's not worth pursuing this unless someone at MySQL identifies this as
> a
> configuration issue on my part. My forehead is pretty flat from this
> one
> now and there're no holes in the brick wall.
>
> Can you suggest a direct connection client (e.g. OCX/DLL) that would
> allow
> me to incorporate an SQL interface into my VB6 application without going
> through ODBC?
>
> Thanks for your help.
>
>
>
> Lawson Cronlund
> lawson@vrtinc.com
> +1(480)308-0641 (Voice)
> +1(602)996-0376 (Fax)
>
>
> -----Original Message-----
> From: SGreen@unimin.com [mailto:SGreen@unimin.com]
> Sent: Thursday, November 10, 2005 8:01 AM
> To: lawson@vrtinc.com
> Cc: 'MySQL Win32 List'
> Subject: RE: Read-only Error On Addnew
>
>
> It may be related to this
>
> http://lists.mysql.com/mysql/190524
> http://lists.mysql.com/mysql/190529 (same thread, just not linked to it
> in
> the archive)
>
> - or this -
>
> There is some reason that Access needs a particular MySQL table setup
> in
> order to work with it as a linked table without throwing a bunch of
> #deleted# values into its display every time you change or add a record.
>
> Follow the directions for hooking Access into MySQL and your program
> should work just fine as I believe Access also uses the .AddNew method
> to
> do several things.
>
> General info: http://dev.mysql.com/doc/refman/5.0/en/odbc-connector.html
> MyODBC vs. Access: http://dev.mysql.com/doc/refman/5.0/en/msaccess.html
> MyODBC vs. VBA and ASP:
> http://dev.mysql.com/doc/refman/5.0/en/msvba.html
>
> Sorry I can't be more specific. Please share what works and what didn't.
>
> Shawn Green
> Database Administrator
> Unimin Corporation - Spruce Pine
>
>
> "Lawson Cronlund" wrote on 11/10/2005 03:56:29 AM:
>
> > I have not been able to get the AddNew method to work in VB6 using
> ODBC
> > 3.51.12 or 3.51.12-2 in conjunction with MySQL 5.0.15 (generally
> available)
> > running on WinXP. Every configuration that I've tried so far has
> resulted
> > in an error 3027 being reported or a problem report being sent back to
> > Microsoft for a serious failure.
> >
> > Does anyone know if this is a known problem or is it a configuration
> issue
> > in how I've set up the ODBC definition?
> >
> > If someone has the above configuration working, could you let me know
> what
> > configuration items I need to set in the ODBC definition.
> >
> > Do I need to drop back to an earlier version of MySQL due to some
> > incompatibility between Win XP, MySQL 5.0.15, and ODBC 3.51.12?
> >
> > Thanks in advance for any help offered.
> >
> >
> >
> > Lawson Cronlund
> > lawson@vrtinc.com
> > +1(480)308-0641 (Voice)
> > +1(602)996-0376 (Fax)
> >
> >
> > -----Original Message-----
> > From: Lawson Cronlund [mailto:lawson@vrtinc.com]
> > Sent: Wednesday, November 09, 2005 12:50 PM
> > To: vps@onepost.net; 'MySQL Win32 List'
> > Subject: RE: Read-only Error On Addnew
> >
> >
> > Thank you for the suggestion.
> >
> > I checked and although the directory/folder for the "ivrcallrecords"
> > database was marked with read-only, the individual tables in the
> directory
> > were not. I changed the directory/folder to reset the read-only
> attribute
> > but that didn't make any difference.
> >
> > When I use a commercially available MySQL graphical client (Navicat) I
>
> can
> > access the tables and modify them. However, this client does not use
> ODBC
> > so my problem probably has something to do with the ODBC settings. As
>
> far
> > as I can tell, I've set the ODBC options the same way that the mysql
> > database is configured. So far all my variations on settings have
> always
> > resulted in the same result of an error 3027 (read-only database).
> >
> > Any help is appreciated.
> >
> > Thank you all.
> >
> >
> >
> > Lawson Cronlund
> > lawson@vrtinc.com
> > +1(480)308-0641 (Voice)
> > +1(602)996-0376 (Fax)
> >
> >
> > -----Original Message-----
> > From: Van Sederburg [mailto:vps@onepost.net]
> > Sent: Wednesday, November 09, 2005 11:25 AM
> > To: lawson@vrtinc.com
> > Subject: Re: Read-only Error On Addnew
> >
> >
> > Make sure the database files themselves are not marked as read only in
>
> the
> > file system.
> >
> > i.e., go to [mysql dir]/data/yourdatabase/
> >
> > Select all files, right click, choose Properties, and clear the Read
> Only
> > checkbox.
> >
> > This typically happens if the database files are moved via CD-Rom or
> some
> > other read only media.
> >
> > Van
> >
> >
> > > I'm new to MySQL so my problem is probably pretty elementary. I'm
> using
> > > ODBC and VB6 to access a database in the MySQL server I've set up.
> The
> > > application is running on the same computer. My problem is that
> when
> > > attempting to add a record to a table (recordset), I get an error
> saying
> > > that the database is read-only. The code snippet included (below my
> > > signature) seems to be the same as the example in the reference
> manual
> > > (ODBC
> > > section) but I consistently get a 3027 error. I presume that this
> is
> a
> > > configuration error on my part but I've been unable to find out what
>
> I'm
> > > doing wrong.
> > >
> > > This occurs with the root UID and password.
> > >
> > > Any suggestions?
> > >
> > > Thanks in advance for whatever help you can offer.
> > >
> > >
> > >
> > >
> > >
> > > Lawson Cronlund
> > > Voice Response Technologies, Inc.
> > > 5717 E. Justine Rd.
> > > Scottsdale, AZ 85254
> > >
> > > lawson@vrtinc.com
> > > +1(480)308-0641 (Voice)
> > > +1(602)996-0376 (Fax)
> > >
> > >
> > >
> > > ========== Error from run time =====3D=
===============3D
> > >
> > > -----------------------------------------------------
> > > | |
> > > | |
> > > | Run-time error '3027': |
> > > | |
> > > | Cannot update. Database or object is read-only. |
> > > | |
> > > | |
> > > -----------------------------------------------------
> > >
> > > ============ code snippet =====3D=
=============3D
> > > ****** Module level declarations *****
> > > Dim wkTest As Workspace
> > > Dim dbTest As Connection
> > > Dim rsTest As Recordset
> > > Dim ODBCStr As String
> > > Dim SQL As String
> > >
> > > ****** Form/Load code *********
> > > Set wkTest =3D CreateWorkspace("", "root", "xxxxxxxx", dbUseODBC)
> > > ODBCStr =3D "ODBC;" & _
> > > "DSN=3DIVRCallRecords;" & _
> > > "UID=3Droot;PWD=3Dxxxxxxxx; OPTION=3D3;"
> > > Set dbTest =3D wkTest.OpenConnection("ivrcallrecords", _
> > > dbDriverNoPrompt, _
> > > False, _
> > > ODBCStr)
> > > SQL =3D "SELECT * FROM logcallstarts;"
> > > Set rsTest =3D dbTest.OpenRecordset _
> > > (SQL _
> > > , dbOpenDynaset, 0, dbOptimistic)
> > > ' , dbOpenDynaset, 0, dbPessimistic)
> > > rsTest.AddNew <<<<<<< error occurs on this line <<<<<<<<<<<
> > > rsTest.Fields![StartDTG] =3D Now
> > > rsTest.Update
> > > .
> > > .
> > > .
> > > =================3D end code snippet =
===============3D
> > >
> > >
> > > --
> > > MySQL Windows Mailing List
> > > For list archives: http://lists.mysql.com/win32
> > > To unsubscribe:
> http://lists.mysql.com/win32?unsub=3Dvps@onepost.net
> > >
> > >
> > >
> >
> >
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe:
> http://lists.mysql.com/win32?unsub=3Dlawson@vrtinc.com
> >
> >
> > --
> > MySQL Windows Mailing List
> > For list archives: http://lists.mysql.com/win32
> > To unsubscribe:
> http://lists.mysql.com/win32?unsub=3Dsgreen@unimin.com
> >
>
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=3Ddanieldaveiga@gma=
il.com
>
>


--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org