Bug with string fields

General usage of Access to MySQL

Moderator: jr

Post Reply
cmorinico
Posts: 5
Joined: Wed Aug 22, 2007 11:40 pm

Bug with string fields

Post by cmorinico »

First, thanks for this beautiful program. I tried many commercial software and none works like this one. But (there is always a but), i found a little bug.

When converting string fields, if a record has a ' character (ie. Bagley's), the program displays a syntax error and does not continue processing other records beyond that one.

I am doing a direct transfer to MySQL 5, latest comunity version as of today.

Thanks for your support.

Claudio Morinico,
Montevideo - Uruguay.
jr
Site Admin
Posts: 500
Joined: Sun Mar 26, 2006 12:28 pm

Post by jr »

Hi Claudio,

That's strange because it works perfectly for me. Can you post the exact error message that you receive and mail a small sample access database that will recreate the problem. You can send the database to info (at) bullzip.com.

Regards,
Jacob
cmorinico
Posts: 5
Joined: Wed Aug 22, 2007 11:40 pm

Post by cmorinico »

Hi Jacob. I sent you an e-mail with the sample database.

Thanks.

Claudio Morinico,
Montevideo - Uruguay.
cmorinico
Posts: 5
Joined: Wed Aug 22, 2007 11:40 pm

Post by cmorinico »

Hi Jacob.

I also found that if i make a dump and try to import it with phpMySQL, it gives me this error with the structure:

------
MySQL said:

# 1075 - Incorrect table definition; there can only be one auto column and it must be defined as a key.
------
cmorinico
Posts: 5
Joined: Wed Aug 22, 2007 11:40 pm

Any news about this problem?

Post by cmorinico »

Any news?
taquitosensei
Posts: 2
Joined: Fri Jul 11, 2008 9:01 pm

Post by taquitosensei »

Do a dump instead of a transfer, then fix that line manually. That's how I fixed this problem.
cmorinico
Posts: 5
Joined: Wed Aug 22, 2007 11:40 pm

Post by cmorinico »

[quote="taquitosensei"]Do a dump instead of a transfer, then fix that line manually. That's how I fixed this problem.[/quote]

That would be a lot of work because I have many tables with this problem.

I already solved this some time ago by buying a converter software from dbconvert.com since I didn't get a reply from jr.

It worked flawlessly for all the databases I had to convert.

Thanks anyway.

Here it is demonstrated that a freeware product is worse than an opensource or paid version. In open source software, you can fix it yourself and give it back to the community. In paid software, you get support from the authors. With freeware you are lost in limbo. Sometimes (like this time) it gives a bad image to the company that develops it. I would never buy a product from BullZip if support or at least a reply would take this long.
jr
Site Admin
Posts: 500
Joined: Sun Mar 26, 2006 12:28 pm

Post by jr »

Hi Claudio,

I can see that the case you are referring to goes way back. I'm sorry that you feel this way. However, I can only agree that freeware support can be slow and sometime missing completely.

In your case I must have forgotten about the issue or maybe had too many things to do. I try to help as many people as possible but with 2000+ downloads a day there may be more than I can cope with.

Even though you have solved your problem by going commercial (which I understand and respect) I still want to fix this if it is an issue. I tried to convert your database with the latest version of Access to MySQL and it gave me the following dumpfile. A direct transfer worked without problems. Do you think it is still an issue with the latest version?

Best regards,
Jacob

# Dump File
#
# Database is ported from MS Access
#--------------------------------------------------------
# Program Version 3.0.84

CREATE DATABASE IF NOT EXISTS `movedb`;
USE `movedb`;

#
# Table structure for table 'Productos'
#

DROP TABLE IF EXISTS `Productos`;

CREATE TABLE `Productos` (
`idProducto` INTEGER NOT NULL AUTO_INCREMENT,
`Nombre` VARCHAR(40) NOT NULL,
`idCatProd` INTEGER NOT NULL,
`ActStock` TINYINT NOT NULL DEFAULT 0,
`MaxDesc` FLOAT NULL NOT NULL,
`idDepC` INTEGER NOT NULL,
`idDepR` INTEGER NOT NULL,
`idMonedaPrecio` INTEGER NOT NULL,
`TipoPrecio` VARCHAR(1) NOT NULL,
`ValorPrecio` DOUBLE NULL NOT NULL,
`Mensaje` VARCHAR(200) NOT NULL,
`Datos` VARCHAR(200) NOT NULL,
`UltimoCosto` DOUBLE NULL NOT NULL,
`idMonedaCosto` INTEGER NOT NULL,
`Codigo` VARCHAR(15) NOT NULL,
`PermitirDescuento` TINYINT NOT NULL DEFAULT 0,
`Discontinuado` TINYINT NOT NULL DEFAULT 0,
`UltimoProveedor` INTEGER,
`RedondearPrecio` TINYINT NOT NULL DEFAULT 0,
`idSeccionDef` INTEGER NOT NULL DEFAULT 0,
`idCatImp` INTEGER NOT NULL DEFAULT 0,
`PermitirTicket` TINYINT NOT NULL DEFAULT 0,
`VentaFraccionada` TINYINT NOT NULL DEFAULT 0,
`CostoPromedio` DOUBLE NULL DEFAULT 0,
`Descuento` FLOAT NULL DEFAULT 0,
INDEX (`idCatProd`),
UNIQUE (`Codigo`),
PRIMARY KEY (`idProducto`),
INDEX (`Nombre`),
INDEX (`idCatImp`)
) TYPE=MyISAM;

#
# Dumping data for table 'Productos'
#

INSERT INTO `Productos` VALUES (191, 'Bailey\'s 3/4', 79, -1, 100, 2, 2, 1, 'F', 421.311475409836, '', '', 0, 1, '9127', -1, 0, 0, 0, 3, 2, -1, -1, 0, NULL);
# 1 records
Post Reply