Recent content by DickyP

You can go on forever in England with this. One more post and I'll stop. Leicester pronounced Lester, and Derby pronounced Darby.

A common pub quiz question - what is the only 5 letter word in English with 4 silent letters? Queue. Then you could try the eccentric names: Mainwaring - pronounced Mannering, and Featherstonehaugh pronounced Fanshaw! Plus place names such as Wymondham pronounced Wind -am.

Not to mention that here in Norfolk we have a village spelled Happisburgh, but pronounced as if spelled Haisborough, like like the nearby Haisborough Sands is spelled! We also have a part of Norwich spelled Costessy, but pronounced locally as Cossy, This caused mirth locally last year when a...

Doing some archaeology on JET (in the Jet Database Engine programmer's Guide pub in 1997!) I found a reference to the Last (and First) aggregate functions, which explicitly says it (they) returns the last value of a set retrieved before formatting (eg, sorts) are applied.

Very similar to the solutions above when I needed to know this information I added a property ".CalledBy" to the form(s) and set this on opening by passing the opening form name in the OpenArgs parameter.

As I said it's a long time ago and I don't have any idea why we did it. Of course, using to API calls method retains a border as well as losing the title bar. Read your article and I expect to have fun playing with it. This is not (necessarily) Change for changes same, unlike the awkward...

The 32 Bit API calls the Title Bar the Option Bar and I'm not talking about the border. The code I used came from the Access 97 Developer's Handbook by Paul Litwin, and it removed the title bar. And just to cofuse Paul Litwin called it the Caption bar!

I'm not actually sure of any actual use for this: fun as an intellectual exercise perhaps. Remember doing something similar back in A97 days where I removed the forms option bar (using API calls) and just used the form header to look like a multi-row option bar. I can't for the life of me...

As you say, it's all relative. We were on holiday from UK in South Carolina when there was a hurricane warning and state governor came on TV to warn people what to do. The next day we were talking to a local who said that he had a dreadful SC accent that most people didn't understand. and that...

I still like Terry Pratchett: "If you trust in yourself and belive in your dreams, and follow your star . . . You'll still get beaten by people who spent their time working hard and learning things who weren't so lazy"

Not surprised - the rest of us can't understand a Liverpudlian at all! 🙂

I understood that 'prove' here was being used in the sense of baking - it helps to expand and fully prepare the rule. I don't swear that this is correct, but merely what I was taught many decades ago in school

The received wisdom is not setting the filter in the report itself but in the DoCd,OpenReport statement in the WhereCondition or , if a stored filter exists, the FilterName parameter. OpenReport (ReportName, View, FilterName, WhereCondition, WindowMode, OpenArgs) As written above the filter is...

In one of today's papers: Uphill struggle for GB Bobsleigh team. (My bolding) I think I see their problem.

You,re obviously not wrong to use .RecordCount but I would tend to use While Not rs.EOF - does avoid problems (on occasion). If you feel that you have to use "Name" as your field name then put it in square brackets when referring to it: eg, rs![Name.]