Recent content by LewisWA02

I don't know what to tell you then because it's doing just what I said it would. It was simply the declaration I had that was wrong. Thanks for your posts.

Ridders, To answer your question: "what would happen if<=txtlow when invert=-1", it would highlight the text box green as in its good because you did less than what could be a problem, versus the other scenario where it would be red to indicate you didn't do enough of what ever the KPI is.

First, let me thank Orthodox Dave for pointing me to the obvious. I use the variable valkpi in a few different instances of code so I had actually declared it as a global variable set to string....so in effect I created my own problem. Changing it lets the code now evaluate all instances as...

Private Sub txtResult_AfterUpdate() valkpi = Me.txtResult If Me.txtinvert = 0 Then If valkpi < Me.txtLow Then Me.txtResult.BackColor = vbRed ElseIf valkpi >= Me.txtLow And valkpi < Me.txtHigh Then Me.txtResult.BackColor = vbYellow ElseIf valkpi >= Me.txtHigh Then...

I have a form where a user inputs a value. The conditional formatting evaluates that value and sets the back color of the text box to the corresponding color. This works ok so long as the number entered is less than 100. Once it's over 100 it seems to evaluate only the first two digits of the...

Unfortunately Ridders, it wasn't that simple. It started working again when our IT replaced all of our old servers over the weekend with new machines. I don't know why that would affect it, but now it works and that's all that matters at this point.

I'm not sure why, but as of yesterday all my databases returned to normal and I can once again save the query from the query builder and it sticks. Thanks to those who tried to help. :confused:

Ranman, I understand that, but it's happening to all the databases I've been working on. Is there a setting that I might have turned on that would cause this to happen?

Doc, That was the first thing I tried. This morning I thought it may be a local setting I'd inadvertently changed, so I opened a blank database and tried to save a query builder there, but I got the same result. I'm just really confused because I don't know what I may have changed, or if a...

I've tried looking this up in a number of different locations, but cannot find an answer. I'm running Access 2016 and up until about a week ago it was going well. Now, when I modify a query in the query builder on a form or report, it won't save. I'll make the changes, save it, close the...

Sorry, here's the working link. http://www.access-programmers.co.uk/forums/showthread.php?t=155950

Has anyone been able to adapt this old code for use with Access 2007? http://www.access-programmers.co.uk/...d.php?t=155950 I don't know enough about Jet to know what I'm missing. Thanks, Billy :banghead:

I had tried a few other ways, but it would only return a blank page if the number wasn't found. I was unable to get it to move to a message box in the event that no record existed. This method does what I wanted it to do, I just kept missing the quotes around the value. Thanks though.

I went back and stepped through it a fiftieth time, and found something I missed. When I hovered over the code it ACTUALLY states: rst!ISBN13 = 1234567891235 and that Me!ISBN = "1234567891235" The quotes meant that the two values weren't dimensioned the same. So I changed the code to this...

Attached is the database I'm working from.