Search results

To remove them, is the only thing that must be done is to change the Display Control in the Lookup tab from Combo Box to Text Box? I'm not asking about what it takes to rewire everything afterwords - simply the removal process.

Again, thanks. That helps clear my confusion. Best wishes, David

Thank you - that helped me see the light more clearly. On a similar note, in the same commandment it says that you shall "Abhor" the use of lookup tables. Does everyone really "Abhor" them? Even the sample Northwind database uses them, as they are a tool. Without them, you would have to...

I'm looking at the ten commandments listed, and the second one says to never let users directly edit the tables. Should it be revised to state that you should never let the users access the tables with totally bound forms (if that is the right jargon to use)? The reason I'm asking is to know...

Thank you. That was quite informative. Now I'm off to put it all together. Best wishes, David

So the full function would look like this? Public Function GetIt(theInput As MyEnum) As String On Error GoTo ErrHandler Select Case theInput Case MyEnum.AValue GetIt = "A Value" Case MyEnum.OtherValue GetIt = "Some Value" Case...

What would be the VBA equivalent of throwing an exception as a default case, to alert tired programmers that they missed something somewhere? Could you post a quick code snippet for the previous example? Thanks.

Since your post left me questioning, and others may also, it appears that for even more clarity you can refer to the enum in the case statements themselves: Public Function GetIt(theInput As MyEnum) As String Select Case theInput Case MyEnum.AValue GetIt = "A Value"...

I'm moving forward with this approach. After consideration, it seems the best option. Yes, it did. Thanks!

Thank you, Banana If I create a wrapper function, such as 'isRegularVisit()', the code will be much prettier - that is a good idea. A question regarding this is that even doing it that way, a DLookup will be at the heart of the function, so in cases where I am toggling through all the cases...

I'm trying to record visits to patients, and there will be five or so visit types. Right now I have a table of these visit types, and it works, but it is difficult to use. For instance, in code, to take action based upon a visit type requires the following, because I refuse to use the ID as a...