Re: Update problem

[Daniel Kasak]

Carlos Daniel Olivas Barba wrote:

>This is the table definition:
>
>'FOLIO_TRASPASO', 'bigint(20)', '', '', '0', ''
>'ORIGEN', 'varchar(15)', '', 'MUL', '', ''
>'DESTINO', 'varchar(15)', '', 'MUL', '', ''
>'FECHA', 'date', 'YES', '', '', ''
>'HORA', 'time', 'YES', '', '', ''
>'CODRESPON', 'varchar(15)', 'YES', '', '', ''
>'TERM', 'varchar(20)', 'YES', '', '', ''
>'STATUS', 'char(1)', 'YES', '', '0', ''
>'A_DISCO', 'enum('Y','N')', 'YES', '', 'N', ''
>'FOLIO_REF', 'int(11)', 'YES', '', '0', ''
>'OBSERVACIONES', 'varchar(200)', 'YES', '', '', ''
>'CONSECUTIVO', 'bigint(20) unsigned', '', 'PRI', '', 'auto_increment'
>'MOTIVO_CANCELADO', 'varchar(200)', 'YES', '', '', ''
>  
>
I'm not sure about VB, but MS Access can't handle bigint columns - 
particularly ones that are primary keys - and *particularly* bigint 
unsigned. How many records have you got anyway? I use mediumint unsigned 
for my primary keys - that gives you plenty of records to play with. int 
will also work. You can try int unsigned if you like.

bigint is probably your problem.

Well ... VB is your problem :)

-- 
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: ([phone] / F: ([phone]
email: dkasak@stripped
website: http://www.nusconsulting.com.au