Search results

Once you've added the new date/time field to the table create a new query. Add the field which contains the month name and the field which will contain the date. In the toolbar at the top there is a button with a drop-down arrow which will let you choose what type of query it is (update...

Is there some reason for keeping the spreadsheets and just having the database as a means to access them rather than importing the data into tables?

What's "it" that you want to do in a query? Again, the OP doesn't specify what you want help with, just that you are currently trying to evaluate strings as parts of dates. Are we talking displaying a 3 character month from a date/time field or creating update queries?

Personally I'd cheat and add a combobox on the login form for the user to select the login type. Although in reality I'd have a single logins table with a text column to signify the access level (or in this case staff / employer / student) to avoid the problem. I would then either base the...

You haven't said what you actually need help with, but I would strongly advise dropping the string olding the 3 digit month and adding a record creation date field instead (or whatever name suits the field) As mentioned in your previous thread you can isolate any part of a date/time field, you...

You can create custom formats. "mmm" should give you the short month name (but I may be wrong, it may be the full month name). I don't seem to be able to find a site which lists all the possibilities, but here's a link to the format function...

You want a crosstab query. However I don't use them so that's the limit of my help! :P Google it (or search this forum) or try the wizard.

OutputTo is the command used in a macro or VBA to save the objects as files (reports to rtf / pdf, queries to xls / csv, etc). The 4th variable is used to define the folder & file name. http://msdn.microsoft.com/en-us/library/aa220433(v=office.11).aspx

I was just hoping to find out if there are any situations where it is better to use select case instead of if, provable or measuarable is purely to try to avoid hearsay. If there's no measurable benefit then it can't be more efficient. If it were then you could measure things like the time...

Sorry, by syntax I meant that each .value taken from a control had the appropriate characters wraping them. The code uses the .tag of a control to define which field to use but it only uses chr(34) to wrap them. Had I read to your post before posting maybe I wouldn't have posted at all, as...

Before setting the .Filter property do this: MsgBox strSQL Then have a look at the string and see if you can find any syntax errors.

You will need to google "VBA thunderbolt automation" to find the functions, etc for thunderbolt. I only use Office here so have never automated thunderbolt.

That's why I was asking if there is any situation which gives a measurable benefit. I never use them. But if there are situations where it's provable that it's better to use them over an If statement then I'd like to know.

Would this work: msgBox Nz(Option3,"No selection")

What event fires the current functionality? There are various events which fire at slightly differnet times such as change, after update, before update. I find an easy way to test which event would be better is to give each one a messagebox (e.g. give on change the following code: MsgBox "On...

Is it "far better" purely for code clarity / style (things that only DB admins will see) or are there situations where using Select Case over If gives a measurable advantage to the end user?

To be perfectly honest, the only option groups I have are legacy ones. As such I'm not the most helpful person regarding troubleshooting them. One of the downsides of being self taught is knowing a way to do things, not necessarily the best way. I'd just go with a couple of checkboxes and...

I've had a quick look online and I can see that , means or. But I don't see anyway to use and. This has further re-enforced my use of If statements over Select case. It could do what you are using Select Case for and it will accept multiple criteria either as and or as or.

Interestingly if you change the control from =2463 to ="2463" (text rather than numeric) it seemed to work without the CInt in the query. No problem, and it goes to show how much easier it is to fix things by tinkering. A long thread discussing it and 8 mins after the .mdb is posted it's...

Aren't the criteria of Select Case statements checked in order? i.e. if you put the 700 to 750 case before the 500 to 900 case then anything between 700 and 750 will have never get to the point of checking against 500 to 900? :edit: I don't really use Select Case much, but the comma...