Theory5 Posted March 6, 2009 Report Share Posted March 6, 2009 I just took this screen shot a few minutes ago when I was trying to make a database for an assignment in school. I followed everything the book said then when I entered the value "8" in a box it said I must keep the number between 0 and 75 (which is what I told it to do in design view). Any other number worked except for 8 and 9. Even my teacher couldnt figure it out and had me save the file on her flash drive so she could study it after class. With errors like these I am suprised Microsoft can stay in business at all. Quote Link to comment Share on other sites More sharing options...
Pyrotex Posted March 6, 2009 Report Share Posted March 6, 2009 Wow, that's awesome! Thanks for bringing this to my attention.There are lots of engineering managers who insist on data being in a "database" when it doesn't really have to be. This might change their minds.;) Quote Link to comment Share on other sites More sharing options...
Theory5 Posted March 6, 2009 Author Report Share Posted March 6, 2009 Glad to help the little people. This is funny, there is an ad on this site for a UI program that works with MS Access 2007 :-) Quote Link to comment Share on other sites More sharing options...
alexander Posted March 9, 2009 Report Share Posted March 9, 2009 Things to ask before installing and using access and things specific to this error are:Are you fully up to date with access patches?Are you fully up to date with windows?.net framework?Is your antivirus running, is it fully up to date and when was the last full scan performed?Is it approved by microsoft?Is your firewall blocking all the events windows developers figured most firewalls would block and did not protect from?Are your socks clean?Did you bring a virgin sacrifice to the computer gods, and when, was it a full moon?Have you ever been in a sect, was it a microsoft approved sect?Did your grandparents ever meet a gypsy and did she tell them that their bad numbers are 8 and 9? (very important)Did you read the newspaper last weekend before it was supposed to be published (that screws everything up)?? You have to make sure all that complies with microsoft minimum requirements before running access, otherwise, well, you get what you got... Clearly one of these you didnt comply with... Quote Link to comment Share on other sites More sharing options...
Theory5 Posted March 9, 2009 Author Report Share Posted March 9, 2009 Things to ask before installing and using access and things specific to this error are:Are you fully up to date with access patches?Are you fully up to date with windows?.net framework?Is your antivirus running, is it fully up to date and when was the last full scan performed?Is it approved by microsoft?Is your firewall blocking all the events windows developers figured most firewalls would block and did not protect from?Are your socks clean?Did you bring a virgin sacrifice to the computer gods, and when, was it a full moon?Have you ever been in a sect, was it a microsoft approved sect?Did your grandparents ever meet a gypsy and did she tell them that their bad numbers are 8 and 9? (very important)Did you read the newspaper last weekend before it was supposed to be published (that screws everything up)?? :doh:yes.yes.yes.yes.yes.yes.no.yes.no.no.no.And what now? :evil:Maybe the computer gods will favor me if I sacrifice a mac......... Quote Link to comment Share on other sites More sharing options...
alexander Posted March 9, 2009 Report Share Posted March 9, 2009 computer gods will not favor you if you sacrifice a MAC, its a pretty child of unix and a BeOS-like kernel, that is doomed to clean up after it's step sisters, XP and Vista, one of which is fat and ugly, tho she think she's beautiful, and the other one is thin, but all made of pieces that didnt fit right.... Mac is a Cinderella of OS-sorts, you will anger the computer gods with a mac sacrifice.... Quote Link to comment Share on other sites More sharing options...
Theory5 Posted March 10, 2009 Author Report Share Posted March 10, 2009 If microsoft learned to release their products AFTER they finish coding them, then there might not have been so many errors in 2007 office and vista. :) Quote Link to comment Share on other sites More sharing options...
alexander Posted March 10, 2009 Report Share Posted March 10, 2009 They did, that's why the release was late, they had to code in all the bugs :) Quote Link to comment Share on other sites More sharing options...
Donk Posted March 11, 2009 Report Share Posted March 11, 2009 It looks to me as if it's reading the data as a text string, not a numeric - 8 and 9 sort higher than 75 if you read them as text. I have to keep Microsoft to stay compatible with the customers, but I've lost count of the number of times I've retired hurt after wrestling with Access :) Quote Link to comment Share on other sites More sharing options...
Theory5 Posted March 11, 2009 Author Report Share Posted March 11, 2009 It looks to me as if it's reading the data as a text string, not a numeric - 8 and 9 sort higher than 75 if you read them as text. I have to keep Microsoft to stay compatible with the customers, but I've lost count of the number of times I've retired hurt after wrestling with Access :) I belive it is set as a number string. Quote Link to comment Share on other sites More sharing options...
alexander Posted March 11, 2009 Report Share Posted March 11, 2009 oh actually, does 18 and 19 work? if so, can you also try using 08 and 09 for input to see if the filter will false-positive it? Quote Link to comment Share on other sites More sharing options...
Slaihne Posted March 17, 2009 Report Share Posted March 17, 2009 Hi there, Dunno if you got this solved, but i had a go myself and found this... If your validation rule for the 'On Hand' field is as follows... Between "0" And "75" You get the behaviour you are experiencing. If it is... Between 0 And 75 It should work properly. Someone mentioned that the field maybe a string type. But apparently it can be a number type while still having the input validated as a string, which seems a bit of an oversight. rgds David Quote Link to comment Share on other sites More sharing options...
Theory5 Posted March 19, 2009 Author Report Share Posted March 19, 2009 Hi there, Dunno if you got this solved, but i had a go myself and found this... If your validation rule for the 'On Hand' field is as follows... Between "0" And "75" You get the behaviour you are experiencing. If it is... Between 0 And 75 It should work properly. Someone mentioned that the field maybe a string type. But apparently it can be a number type while still having the input validated as a string, which seems a bit of an oversight. rgds David I thought it put stuff in "" automatically? Quote Link to comment Share on other sites More sharing options...
C1ay Posted March 19, 2009 Report Share Posted March 19, 2009 I thought it put stuff in "" automatically? Sometimes it does and you have to remove them... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.