Search results

I believe you are correct with that, and on that note I wish I did have a table like that. I am using access to run custom reports off of our internal tracking system ( linked table mostley). This system is from Best software ( sage?) and is severly limited. So with no table like this....i'm...

I have a combobos using a table to look up its values, no problem. The table could have several identical values to place in the combo box ( same city, State multiplt times). I want to group these so that the city, state will only show once in the combobox, hence makiing the list a little...

you are the MAN! So I guess I had somewhat of the right idea, just not sure how to go about these things yet. this forum has been great! Thanks again Ken

Good morning All, First, I want to Thank Ken Hig for helping me on using CASE SELECT for something similar yesterday. I have a report with a field RCSN, This can have several different values in it. Based on these values I want an unbound text field "RCModel" to display certain values: 1 - If...

YAAHHHOOOOO!. Thanks again for all you time!!!!!! :) :D ;)

tried that and now in my report i get "#NAME?" in my CFModel field ??? ideas why? In CFModel control source in the report i have =CFModel() this should call the function correctly right?

Its been a long day... I get a syntax error on the CASE LIKE lines. EDIT: from the Access help file "Note that Is and Like can't be used as comparison operators in a Select Case statement." Function CFModel(CFSN As String) As String Select Case CFSN Case like "EG1*" CFModel = "1...

i thought that also, but i doesn't like the "like". what i just found in another post fixed all: Function CFModel() Select Case CFSN Case Left(CFSN, 3) = "EG1" CFModel = "1 GB" Case Left(CFSN, 3) = "FN1" CFModel = "2 GB" Case Left(CFSN, 3) = "RQ1" CFModel...

The fields are pretty stable, we won't add to these to often. I started to create the module for the CFSN. I need a bit of help on the CASE ELSE line if you don't mind. IF no matching case then show the value of CFSN in the CFModel field. Function CFModel() Select Case CFModel Case Is =...

I guess the bullet isn't really that bad. If I do the same evaluation for these fields in other reports, I can then call the functions as needed. Thanks Ken

no, each of the 10 has their own "source". I was thinking of a mudule kinda like this, 1 select case for each of the 10 fields. Function select case [CFSN] Case IS...... Case IS...... Case Else End case Select case [field2] Case IS..... Case IS..... Case Else End Case...

I believe I found a post by Pat Hartman that answered my question - yes it would be better to do this in a module. Now a quick question, I have 10 fields in my report using the IIF function. Can I do 1 module with 10 different case statement sections, and call this module in my 10 fields in...

I've seen several threads on using =IIF in a report field. I am wondering if VBA would be a better way to do the following? report with a field evaluating a 2nd field. In my control source for the 1st field: =IIf([CFSN] Like "EG1*","1 GB",IIf([CFSN] Like "FN1*","2 GB",IIf([CFSN] Like...

I have been wanting to fool around with MS access over web pages ( more powerful than DAP) but haven't had the time. I believe (don't take my word for it) something like Macromedia's ColdFusion MX7 would be a good tool to start with. their dreamweaver MX2004 product is awesome for doing...

no need to creat more tables. goto modules, new, and paste in the code from above. when the you close the code window, you will be prompted to save the new module - yes, and call it something like -- DateDifference then in your reports or wherever you can use this in your control source ---...

You can do a search for something like "datediffernce" and get quite a few posts. I found ( and use) the code below. create a module called -- whatever you want. and paste in the below code, then call it using DateDiffW. 'Function to calculate business days, does NOT consider...

If I understand the question correctly, yes, you have to copy the code from each fields afterupdate_event into the forms Current_event. Its alot of copying and pasteing but it will work. I only do it for 3 different fields so it wasn't as bad for me, you have 8 fields.

I don't print barcodes, but I do scan several hundred different ones into my DB. It works great for data entry ( saves on human error ), searching..... The scan gun should have a users manual and a programmers manual ( look on the manufacturers website). The programmers manual is for doing...

Look at the version oy your DB I am posting. I used the ISNULL for determining the field has data or not. You can then add this to each one of your fields. If field 2 is null then...... If field 3 is null then.... There might be a better way of doing it, but this is what i have done in the...

1 - properties of the first date field. 2 - Event Tab 3 - AfterUpdate event procedure. In the code window copy the below code, substituting your field names for 2, 3, and 4. this will be inbetween the "PRIVATE SUB" and "END SUB" If Me.DateField1 = True Then Me.DateField2.Visible = False...