Recent content by Mile-O

Thanks so much. Really appreciated. Yes, the Word doc is no issue. I'm currently on a Mac, and apps can at least convert Word. I'll be able to take this old dataset and play around with it in Tableau now. :)

Try now. :) https://www.dropbox.com/s/s5rbhcf3l2zb29f/Witchcraftsurvey_download.mdb?dl=0

The download is here. It may ask for a name/email address, but I reckon you can enter anything. It's an old archived page off a university site. https://witches.shca.ed.ac.uk/index.cfm?fuseaction=home.download Though I'm not sure how you can get it back to me...other than email or transfer...

HI All, I've found a dataset online that's been archived back in 2003 using the old Access 97 .mdb format/extension. Since backward capability this format was done away with back with Access 2013, I can't open the dataset to use it. Is anyone still working with a Access 2003/2007/2010 (or has...

Sam Summers; that's a username blast from the past... One quick solution would be to, in the query design view, right click on whatever your field is your crosstab's column heading and enter the Column Headings, separated by commas (i.e. "Q1","Q2","Q3","Q4") Or, if the list is in somewhere in...

Another useful thing to note is the Static keyword. So, rather than Dim, you can use Static, and the variable value will be retained. Static myCounter As Long

I would have thought IsNull(DateReceived) would be better written as DateReceived Is Null in this context. Anyway, CountMsg = DCount("*", "[F_Tbl_Msg]", "([ToUserID]= """ & [TempVars]![TempUser] & """ Or [ToUserID] = ""All"") And [DateReceived] Is Null") Personally, I'd do away with all...

Cheers. Though these days I try not to be reminded. :p

I added tags so that some code doesn't look like this: Dim intExample As Integer For intExample = 1 To 10 MsgBox "Example " & intExample Next intExample But instead looks like this. Dim intExample As Integer For intExample = 1 To 10 MsgBox "Example " & intExample Next intExample...

Apologies, I tried to add adding [CODE] [/CODE] tags to the original post, but the code having a field called [CODE] threw it off.

A table structure, something basic like this, should do exactly what you are wanting to do without having to store calculated values in your table. tblMaterialTypes MaterialTypeID (Autonumber, primary key) MaterialType (Text) tblMaterials MaterialID (Autonumber, primary key) MaterialName...

You're in Access now; leave the Excel thinking at the door. You can calculate in queries and make these queries your form's RecordSource, rather than a table. The control's ControlSource need only do the calculation for display purposes. You need never store the result of the calculation.

I told him as much yesterday. http://www.access-programmers.co.uk/forums/showthread.php?t=284693

ALARM BELL! Do not do this. If you are calculating it at run-time, you always calculate it at run-time. This is part and parcel of database design in that you do not store calculated values. (See: normalisation.) Quick reason why: If you have a field called Quantity and a record's value is 2...

Unless you need a very specific unique code structure for your objects then the autonumber should suffice. That you are losing numbers through deletes shoudl not matter as the number is ultimately meaningless and should remains that way, Or, in other words, don't ascribe any logic or meaning to...