Unbound to bound

suziem

I store a calculation in an unbound field. Based on this value another value must be stored in a bound field eg <100 = A; <200 = B etc.but it only updates the bound field once I've clicked on it. Any ideas what I'm doing wrong?

kstevens

Can you post the code that is setting the value of the bound field.

suziem

Expand|Select|Wrap|Line Numbers

 If Me.Text48.Value > 13060694016# Then

  Me.OverallMaintenanceImportance.Value = "A"

End If

If Me.Text48.Value > 11612804 Or Me.Text48 < 13060694016# Or Me.Text48 = 13060694016# Then

  Me.OverallMaintenanceImportance.Value = "B"

End If

If Me.Text48.Value > 10161616 Or Me.Text48 < 11612804 Or Me.Text48 = 11612804 Then

  Me.OverallMaintenanceImportance.Value = "C"

End If

If Me.Text48.Value > 8710428 Or Me.Text48 < 10161616 Or Me.Text48 = 10161616 Then

  Me.OverallMaintenanceImportance.Value = "D"

End If

If Me.Text48.Value > 7259240 Or Me.Text48 < 8710428 Or Me.Text48 = 8710428 Then

  Me.OverallMaintenanceImportance.Value = "E"

End If

If Me.Text48.Value > 5804752 Or Me.Text48 < 7259240 Or Me.Text48 = 7259240 Then

  Me.OverallMaintenanceImportance.Value = "F"

End If

If Me.Text48.Value > 4553564 Or Me.Text48 < 5804752 Or Me.Text48 = 5804752 Then

  Me.OverallMaintenanceImportance.Value = "G"

End If

If Me.Text48.Value > 2902376 Or Me.Text48 < 4553564 Or Me.Text48 = 4553564 Then

  Me.OverallMaintenanceImportance.Value = "H"

End If

If Me.Text48.Value > 1451189 Or Me.Text48 < 2902376 Or Me.Text48 = 2902376 Then

  Me.OverallMaintenanceImportance.Value = "I"

End If

If Me.Text48.Value < 1451189 Or Me.Text48 = 1451189 Then

  Me.OverallMaintenanceImportance.Value = "J"

End If

Frinavale

I think you might be interested in using a switch.....

suziem

Thanks a million. I have used the If ElseIf command and it works like a charm. Much appreciated

FishVal

Impressed ... very impressed.

Would you like to read the following?
Grouping Query Range

P.S. BTW, does it really work?

NeoPa

Am I too late to the party?

I strongly suggest using a Select Case construct for this code. Neater & faster of execution than ElseIf .

BTW, you don't include the code which would have indicated where your existing code was running. I suggest if you put some code in the AfterUpdate event procedure of your unbound control, that it will behave as you hope.

Good luck and Welcome to Bytes!

Frinavale

Thanks NeoPa!
I didn't know if it was called a Switch or a Select Case....just grabbed the first reasonable thing I saw that google showed came up with.

:)

-Frinny

Frinavale

Is my previous link even relevant?

It's weird but the switch function looks like it does the same sort of thing as a Select Case. The worst part of my confusion is that switch is the C++/C# equivalent to a select case....when I tried to google "access" and "select" I kept coming across SQL references so I changed the search to switch and tada some random function that I thought was relevant (but now I'm wondering about).

Just curious: do Access developers ever use that switch function I found googling?

NeoPa

Quote:

Originally Posted by Frinavale

Just curious: do Access developers ever use that switch function I found googling?

Yes, but not much.

I guess you were trawling for some questions to answer & found Access huh :D

The Switch() is a natural find for a C/C++ developer. I went there myself some while back. In effect though, it is more similar to multiple ElseIfs. The Select Case is much more similar to the C Switch statement than Switch() is. In the Switch() function the whole comparison is evaluated for all of the comparisons, regardless of where the first true result is found. With Select Case, however, the left side is evaluated only the once, and the case statements are compared with it as they are reached. Once a true result is found no further Case statements are reached.

@Frinny Call me if you're online now.

FishVal

Did anybody notice that actually all but the first and the last conditions always evaluate to True?

P.S. Array/Loop or, in DB application, Table/SQL could do this simple lookup efficiently and flexibly while Switch and If <removed as per site rules>. :P

Frinavale

Quote:

Originally Posted by NeoPa

Yes, but not much.

I guess you were trawling for some questions to answer & found Access huh :D

Not quite. Was looking to bump this question because it was moderated for some reason....thought I could answer it. Obviously didn't do a very good job of it though :P

Quote:

Originally Posted by NeoPa

@Frinny Call me if you're online now.

Think I missed ya.

NeoPa

Quote:

Originally Posted by Frinavale

Obviously didn't do a very good job of it though :P

It was a decent stab even for an Access person.

It was a pleasant surprise to have you visit this neck of the woods. Don't be put off.

NeoPa

Quote:

Originally Posted by FishVal

Did anybody notice that actually all but the first and the last conditions always evaluate to True?

I didn't :(

I expect the intended logic is obvious enough in this case though.

Quote:

Originally Posted by FishVal

P.S. Array/Loop or, in DB application, Table/SQL could do this simple lookup efficiently and flexibly while Switch and If <removed as per site rules>. :P

Good call. I generally use a table only if the number of items is enough to make it worth the overhead (development rather than time or space). I set the threshold lower for exact match lists. This task may well fit into this category.

Please explain what was removed. I think I'm probably having a dumb moment, but I'm missing the joke here :S

kstevens

Does anybody else think that these should be And... not Or.

Expand|Select|Wrap|Line Numbers

 If Me.Text48.Value > 11612804 And Me.Text48 <= 13060694016#  

Me.OverallMaintenanceImportance.Value = "B"

I removed the last expression and put the <= to do both Suziem

suziem

Agreed but rusted. Haven't done programming for a while. I also changed it to elseif and it worked like a charm

NeoPa

Quote:

Originally Posted by kstevens

Does anybody else think that these should be And... not Or.

That's basically what Fish was saying in post #11 ;)

You're absolutely right of course K.

Frinavale

I still think it looks messy and could be much nicer, cleaner, faster code if it was a Select Case :)

(PS I checked out Access 2007 last night... all I can say is wow, there's more to it than I thought)

NeoPa

Quote:

Originally Posted by Frinavale

I still think it looks messy and could be much nicer, cleaner, faster code if it was a Select Case :)

You're absolutely right of course Frinny, but I suspect the OP is a bit nervous about doing anything new having only recently returned to coding.

Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

re: Unbound to bound

Similar Microsoft Access / VBA bytes

/bytes/development

/bytes/it

/bytes/about