Subject |
Re: autoincrement problem |
From |
Charlie <tm@tc.com> |
Date |
Wed, 18 Oct 2023 09:12:18 -0400 |
Newsgroups |
dbase.getting-started |
Attachment(s) |
COINS.DBF, COINS.MDX |
OK Ken, I will send everything. I am not trying to hide any data, but was hiding what I am doing. I recently retired from my electric train business and needed something to do so I am working on another hobby interest of mine solely for my personal use at this time. I love coding, and the coding itself has kept me busy so far in my retirement.
I added the sku field yesterday to use instead of the autoint field just in case this can\\\'t be fixed. But the autoint is best for the job.
Ken Mayer Wrote:
> On 10/17/2023 11:18 PM, Charlie wrote:
> > structure or entire table?
> >
>
> Table, indexes, dbt file if any ... it\\\'s hard to reproduce a problem
> without the whole table. If the data is a problem (private/proprietary),
> can you copy the table and provide just a small amount of even \\\"dummy\\\"
> data, so we have something to work with?
>
> Ken
>
> --
> *Ken Mayer*
> Ken\\\'s dBASE Page: http://www.goldenstag.net/dbase
> The dUFLP: http://www.goldenstag.net/dbase/index.htm#duflp
> dBASE Books: http://www.goldenstag.net/dbase/Books/dBASEBooks.htm
> dBASE Tutorial: http://www.goldenstag.net/dbase/Tutorial/00_Preface.htm
> dBASE Web Tutorial: http://www.goldenstag.net/dbase/WebTutorial/00_Menu.htm
> dBASE DOS to Windows Tutorial:
> http://www.goldenstag.net/dbase/DtoWTutorial/00_Menu.htm
>
|
|