From: Lynn Allen Organization: What? Newsgroups: comp.databases.filemaker Date: Wed, 9 Feb 2011 19:45:26 -0800 Message-ID: <4d535f34@news.bnb-lp.com> References: <3d7fdf39-33b6-477a-b969-a849c718382a@s41g2000vbw.googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: any ideas to workaround Serial Number limitation of 2147483647 User-Agent: Unison/1.7.9 NNTP-Posting-Host: pool-74-100-83-23.lsanca.fios.verizon.net X-Trace: news.bnb-lp.com 1297309492 pool-74-100-83-23.lsanca.fios.verizon.net (9 Feb 2011 22:44:52 -0400) Lines: 46 X-Authenticated-User: vca037 X-DMCA-Complaints: Send abuse or DMCA complaints to abuse@bnb-lp.com X-DMCA-Complaints: The subject line should contain only the 4 letters DMCA Path: csiph.com!eeepc.pasdenom.info!news.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-1.proxad.net!feeder.news-service.com!news.netcologne.de!newsfeed-fusi2.netcologne.de!news.swapon.de!feedme.ziplink.net!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.bnb-lp.com!not-for-mail Xref: csiph.com comp.databases.filemaker:1420 On 2011-02-09 15:11:11 -0800, George Lewycky said: > > > We have an old Filemaker Pro 5.0 application that we are replacing to > SQL Server, VB .NET and currently > our real serial number is 2147483647 and whenever we do a range > calculation this is its maximum and the next number in sequence > becomes "-2147483648" etc etc (see below) > > http://groups.google.com/group/comp.databases.filemaker/browse_thread/thread/62bcdfef72bbeeab/bb3a7c86693c4bea?hl=en&lnk=gst&q=billion Has > > anyone encountered this and found a work around > > > TIA > > George It seems unlikely that you have that many records in FM just from a capacity standpoint, so there must be many serials going unused. I am presuming this serial is used as a key in one or several tables. Since you don't plan on using FM going forward I would create a field in whatever is the base parent table called "reserialize" and enter sequential serials starting from 1 in that table. Then in the child tables, using the original key field and the new serial field as a "translator", pull the new serial into the foreign key fields of the child records. (Obviously work on a copy of your files, belt and suspenders when working with keys) Lather, rinse, repeat, until all tables have the new serials in their key fields. Test and check to make sure all relationship are functioning. Now you'll be nowhere near the limit. Rather than trying to overcome a programmatic limitation, kludge the data. ;) -- Lynn Allen -- www.semiotics.com Member FBA FM 10 Certified Developer