Re: Autonum broken

Normalisation was not the right word. Each row has only two columns - "id" INT and "description" VARCHAR. So the rows did not, indeed could not, contain data relating to more than one entity. It was the /table/ which contained mixed data. The description column had data for two different cat

Re: Autonum broken

John Morrison wrote: In the interests of better normalisation I decided to divide one table's data between two tables. So I created another table and copied selected rows into it. I'd love to know how you believe that copying rows to another table is better for normalization. If you mean

Re: Autonum broken

Hello Paul Many thanks. I won't try that again, then. John In article , Paul DuBois wrote: > At 12:37 + 1/6/03, John Morrison wrote: > >Hello everyone > > > >I am developing an application with MySQL v3.23.33 (MyISAM tables) using > >Microsoft Visual

Re: Autonum broken

At 12:37 + 1/6/03, John Morrison wrote: Hello everyone I am developing an application with MySQL v3.23.33 (MyISAM tables) using Microsoft Visual Basic and ODBC v3.520.6019.0. My OS is MS Windows 2000 I have just had an interesting issue crop up concerning gaps in autonumbering. In the inte

Autonum broken

Hello everyone I am developing an application with MySQL v3.23.33 (MyISAM tables) using Microsoft Visual Basic and ODBC v3.520.6019.0. My OS is MS Windows 2000 I have just had an interesting issue crop up concerning gaps in autonumbering. In the interests of better normalisation I decided to d