Guest rdarne Posted June 10, 2008 Posted June 10, 2008 I have a strange problem with numbers on a computer in my office. It appears as though integer values are not recognized. For instance, Access has a version number of 18.4. On this computer, it shows as 18.45649382 (not exactly, but a long decimal number). In an Access form that counts records, all numbers have a long decimal after them. This also occurs in a webstore form that a user can enter a price for a product. When you try to enter 110 or 110.00, it tells you that it must be an integer. If you add many decimal points (110.003344566) it will recognize and accept this number. I think this may also affect MS Outlook, which has this header atop every message: "by Saturday, January 01, 4501 12:01 AM. Completed on by Saturday, January 01, 4501 12:01 AM. You attempted to recall this message on by Saturday, January 01, 4501 12:01 AM. This item has been marked to be delivered after by Saturday, January 01, 4501 12:01 AM." Thanks for any help you can provide.
Guest db.·.. > Posted June 10, 2008 Posted June 10, 2008 Re: Integer Problem? the formatting for those particular fields in access can be changed from integer to dollar value. the forms will have to be opened and edited. basically, whom ever created the access forms/templates left the default field setting as integer. -- db·´¯`·...¸><)))º> "rdarne" <rdarne@discussions.microsoft.com> wrote in message news:752DF23B-8D6A-44DA-9479-042D08FF82DA@microsoft.com... >I have a strange problem with numbers on a computer in my office. It appears > as though integer values are not recognized. For instance, Access has a > version number of 18.4. On this computer, it shows as 18.45649382 (not > exactly, but a long decimal number). In an Access form that counts records, > all numbers have a long decimal after them. > > This also occurs in a webstore form that a user can enter a price for a > product. When you try to enter 110 or 110.00, it tells you that it must be an > integer. If you add many decimal points (110.003344566) it will recognize and > accept this number. > > I think this may also affect MS Outlook, which has this header atop every > message: > "by Saturday, January 01, 4501 12:01 AM. > Completed on by Saturday, January 01, 4501 12:01 AM. > You attempted to recall this message on by Saturday, January 01, 4501 12:01 > AM. > This item has been marked to be delivered after by Saturday, January 01, > 4501 12:01 AM." > > Thanks for any help you can provide.
Guest rdarne Posted June 10, 2008 Posted June 10, 2008 Re: Integer Problem? Thanks for the reply. We are running MySQL as the DB and Access as a front end. His is the only computer that has these strange number problems. Each of the other users show the correct numbers. I can even open his copy of the front end from a different computer and it will work. "db.·.. ><))) ·>` .. ." wrote: > the formatting for those > particular fields in access > can be changed from integer > to dollar value. > > the forms will have to > be opened and edited. > > basically, whom ever > created the access > forms/templates left > the default field setting > as integer. > > -- > > db·´¯`·...¸><)))º> > > > "rdarne" <rdarne@discussions.microsoft.com> wrote in message > news:752DF23B-8D6A-44DA-9479-042D08FF82DA@microsoft.com... > >I have a strange problem with numbers on a computer in my office. It appears > > as though integer values are not recognized. For instance, Access has a > > version number of 18.4. On this computer, it shows as 18.45649382 (not > > exactly, but a long decimal number). In an Access form that counts records, > > all numbers have a long decimal after them. > > > > This also occurs in a webstore form that a user can enter a price for a > > product. When you try to enter 110 or 110.00, it tells you that it must be an > > integer. If you add many decimal points (110.003344566) it will recognize and > > accept this number. > > > > I think this may also affect MS Outlook, which has this header atop every > > message: > > "by Saturday, January 01, 4501 12:01 AM. > > Completed on by Saturday, January 01, 4501 12:01 AM. > > You attempted to recall this message on by Saturday, January 01, 4501 12:01 > > AM. > > This item has been marked to be delivered after by Saturday, January 01, > > 4501 12:01 AM." > > > > Thanks for any help you can provide. > >
Guest db.·.. > Posted June 10, 2008 Posted June 10, 2008 Re: Integer Problem? hmm? perhaps you should open that front end on the computer with the issue and simply double check that the fields in question are using the correct formatting. there are differently methodologies available and perhaps the one being used is that this particular pc has its own frontend installed locally. -- db·´¯`·...¸><)))º> "rdarne" <rdarne@discussions.microsoft.com> wrote in message news:A98C1500-EACB-40E2-A2F6-D36F469DE819@microsoft.com... > Thanks for the reply. We are running MySQL as the DB and Access as a front > end. His is the only computer that has these strange number problems. Each of > the other users show the correct numbers. I can even open his copy of the > front end from a different computer and it will work. > > "db.·.. ><))) ·>` .. ." wrote: > >> the formatting for those >> particular fields in access >> can be changed from integer >> to dollar value. >> >> the forms will have to >> be opened and edited. >> >> basically, whom ever >> created the access >> forms/templates left >> the default field setting >> as integer. >> >> -- >> >> db·´¯`·...¸><)))º> >> >> >> "rdarne" <rdarne@discussions.microsoft.com> wrote in message >> news:752DF23B-8D6A-44DA-9479-042D08FF82DA@microsoft.com... >> >I have a strange problem with numbers on a computer in my office. It appears >> > as though integer values are not recognized. For instance, Access has a >> > version number of 18.4. On this computer, it shows as 18.45649382 (not >> > exactly, but a long decimal number). In an Access form that counts records, >> > all numbers have a long decimal after them. >> > >> > This also occurs in a webstore form that a user can enter a price for a >> > product. When you try to enter 110 or 110.00, it tells you that it must be >> > an >> > integer. If you add many decimal points (110.003344566) it will recognize >> > and >> > accept this number. >> > >> > I think this may also affect MS Outlook, which has this header atop every >> > message: >> > "by Saturday, January 01, 4501 12:01 AM. >> > Completed on by Saturday, January 01, 4501 12:01 AM. >> > You attempted to recall this message on by Saturday, January 01, 4501 12:01 >> > AM. >> > This item has been marked to be delivered after by Saturday, January 01, >> > 4501 12:01 AM." >> > >> > Thanks for any help you can provide. >> >>
Guest rdarne Posted June 11, 2008 Posted June 11, 2008 Re: Integer Problem? Thanks. I checked that out and the fields are correct. He actually runs this front end from a network drive. "db.·.. ><))) ·>` .. ." wrote: > hmm? > > perhaps you should open > that front end on the > computer with the > issue and simply double > check that the fields > in question are using > the correct formatting. > > there are differently > methodologies available > and perhaps the one > being used is that this > particular pc has its > own frontend installed > locally. > > -- > > db·´¯`·...¸><)))º> > > > "rdarne" <rdarne@discussions.microsoft.com> wrote in message > news:A98C1500-EACB-40E2-A2F6-D36F469DE819@microsoft.com... > > Thanks for the reply. We are running MySQL as the DB and Access as a front > > end. His is the only computer that has these strange number problems. Each of > > the other users show the correct numbers. I can even open his copy of the > > front end from a different computer and it will work. > > > > "db.·.. ><))) ·>` .. ." wrote: > > > >> the formatting for those > >> particular fields in access > >> can be changed from integer > >> to dollar value. > >> > >> the forms will have to > >> be opened and edited. > >> > >> basically, whom ever > >> created the access > >> forms/templates left > >> the default field setting > >> as integer. > >> > >> -- > >> > >> db·´¯`·...¸><)))º> > >> > >> > >> "rdarne" <rdarne@discussions.microsoft.com> wrote in message > >> news:752DF23B-8D6A-44DA-9479-042D08FF82DA@microsoft.com... > >> >I have a strange problem with numbers on a computer in my office. It appears > >> > as though integer values are not recognized. For instance, Access has a > >> > version number of 18.4. On this computer, it shows as 18.45649382 (not > >> > exactly, but a long decimal number). In an Access form that counts records, > >> > all numbers have a long decimal after them. > >> > > >> > This also occurs in a webstore form that a user can enter a price for a > >> > product. When you try to enter 110 or 110.00, it tells you that it must be > >> > an > >> > integer. If you add many decimal points (110.003344566) it will recognize > >> > and > >> > accept this number. > >> > > >> > I think this may also affect MS Outlook, which has this header atop every > >> > message: > >> > "by Saturday, January 01, 4501 12:01 AM. > >> > Completed on by Saturday, January 01, 4501 12:01 AM. > >> > You attempted to recall this message on by Saturday, January 01, 4501 12:01 > >> > AM. > >> > This item has been marked to be delivered after by Saturday, January 01, > >> > 4501 12:01 AM." > >> > > >> > Thanks for any help you can provide. > >> > >> > >
Guest db.·.. > Posted June 11, 2008 Posted June 11, 2008 Re: Integer Problem? ok, it sounds like you did well to double check. just to touch base, you do know that the datafile fields and the form fields are separate and each require to be formatted. based on the methodology the datafile would be formatted correctly since everyone is linked to it. it would be the frontend forms on the individual pc that may be the problem i suppose i am rusty, but based on my experience it would be inefficient not to have each pc with a locally installed frontend/forms. but never the less, your system must be optimized differently. here are a couple of sites that can provide some help: one is a newsgroup where you can repost your question and the other is general trouble shooting for access. http://www.microsoft.com/office/community/en-us/FlyoutOverview.mspx http://support.microsoft.com/Default.aspx?scid=ph%3ben-us%3b2509&sid=216 i had hoped that the issue was a simple matter of formatting. lets see what the others links can provide for you. perhaps if you do find a solution you can post it on this thread to conclude it. it will be helpful for others who encounter a similar problem like yours. -- db·´¯`·...¸><)))º> "rdarne" <rdarne@discussions.microsoft.com> wrote in message news:C87CE98E-56B7-462A-AB6A-684FD6150D8A@microsoft.com... > Thanks. I checked that out and the fields are correct. He actually runs this > front end from a network drive. > > "db.·.. ><))) ·>` .. ." wrote: > >> hmm? >> >> perhaps you should open >> that front end on the >> computer with the >> issue and simply double >> check that the fields >> in question are using >> the correct formatting. >> >> there are differently >> methodologies available >> and perhaps the one >> being used is that this >> particular pc has its >> own frontend installed >> locally. >> >> -- >> >> db·´¯`·...¸><)))º> >> >> >> "rdarne" <rdarne@discussions.microsoft.com> wrote in message >> news:A98C1500-EACB-40E2-A2F6-D36F469DE819@microsoft.com... >> > Thanks for the reply. We are running MySQL as the DB and Access as a front >> > end. His is the only computer that has these strange number problems. Each >> > of >> > the other users show the correct numbers. I can even open his copy of the >> > front end from a different computer and it will work. >> > >> > "db.·.. ><))) ·>` .. ." wrote: >> > >> >> the formatting for those >> >> particular fields in access >> >> can be changed from integer >> >> to dollar value. >> >> >> >> the forms will have to >> >> be opened and edited. >> >> >> >> basically, whom ever >> >> created the access >> >> forms/templates left >> >> the default field setting >> >> as integer. >> >> >> >> -- >> >> >> >> db·´¯`·...¸><)))º> >> >> >> >> >> >> "rdarne" <rdarne@discussions.microsoft.com> wrote in message >> >> news:752DF23B-8D6A-44DA-9479-042D08FF82DA@microsoft.com... >> >> >I have a strange problem with numbers on a computer in my office. It >> >> >appears >> >> > as though integer values are not recognized. For instance, Access has a >> >> > version number of 18.4. On this computer, it shows as 18.45649382 (not >> >> > exactly, but a long decimal number). In an Access form that counts >> >> > records, >> >> > all numbers have a long decimal after them. >> >> > >> >> > This also occurs in a webstore form that a user can enter a price for a >> >> > product. When you try to enter 110 or 110.00, it tells you that it must >> >> > be >> >> > an >> >> > integer. If you add many decimal points (110.003344566) it will >> >> > recognize >> >> > and >> >> > accept this number. >> >> > >> >> > I think this may also affect MS Outlook, which has this header atop >> >> > every >> >> > message: >> >> > "by Saturday, January 01, 4501 12:01 AM. >> >> > Completed on by Saturday, January 01, 4501 12:01 AM. >> >> > You attempted to recall this message on by Saturday, January 01, 4501 >> >> > 12:01 >> >> > AM. >> >> > This item has been marked to be delivered after by Saturday, January 01, >> >> > 4501 12:01 AM." >> >> > >> >> > Thanks for any help you can provide. >> >> >> >> >> >>
Recommended Posts