John W. Colby
jwcolby at colbyconsulting.com
Thu May 19 06:21:32 CDT 2005
One of the Sperry Univac (I believe) minis I worked on in Navy was an 18 bit word, and one of the mainframes was a 36 bit word. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly Sent: Thursday, May 19, 2005 1:32 AM To: Access Developers discussion and problem solving Subject: Re: Integers vs. Long Integers Was: RE: [AccessD] Global Variable I worked on the Honewell 6000 series mainframe where the the word size was 36 bits John W. Colby wrote: >ROTFL so you're saying even THAT is wrong? > ><grin> > >John W. Colby >www.ColbyConsulting.com > >Contribute your unused CPU cycles to a good cause: >http://folding.stanford.edu/ > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart >McLachlan >Sent: Wednesday, May 18, 2005 7:09 PM >To: Access Developers discussion and problem solving >Subject: RE: Integers vs. Long Integers Was: RE: [AccessD] Global Variable > > >On 18 May 2005 at 18:31, John W. Colby wrote: > > > >>NONE of my experience says it takes "3 steps to do with an integer >>what it takes 1 step to do with a long". About the only thing that I >>would say is correct is "An integer is a 16 bit variable". >> >> >> > >Bzzzzzt. >An integer is a whole number. In today's PCs they are normally 8,16,32 or >64 bits in size. > > > > > > > > > -- Marty Connelly Victoria, B.C. Canada -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com