Search results

I'd support Doc as the "one moderator to rule them all".

I don't agree that they need to be neutral in arguments (political or otherwise); they're allowed to have and express opinions. I would say that they should set a high bar in how those arguments are presented.

Regarding "I thought the mods were supposed to monitor things, not spend all day arguing with people who have a different opinion to theirs." Mods are typically "power users" of a forum that are asked at some point to help moderate that forum. I'm guessing their heavy use of the forum means...

Sounds like your macro is adding the record via the form rather than via recordset or SQL? How about toggling the setting at the beginning/end of your macro?

Keep in mind I mentioned we use the TV's remote. In addition to the up/down/left/right buttons around the OK button, it also has channel and volume up/down buttons. Those are the ones that work to change channels.

We have YTTV and can use the up/down buttons on the TV's remote to change channels. There's also a last channel feature, though it's a bit hidden.

Go outside and take pictures of them and their license plate, send to @moke123 :devilish:

I lived in NV but was in Monterey, CA with my wife at a small gathering of her family. We were all talking, playing cards and such with no TV or radio on. We didn't find out about it until we got in the car to head home and heard about it on the radio. This would have been 5-6 hours after it...

Welcome Jeff!

The correct delimiter for a date field is #.

By the way, you may not realize you're not seeing the entire SQL string in that row source. If you copy it you'll see: SELECT [Unit Kerja Peserta].[ID Unit Kerja], [Unit Kerja Peserta].[Nama Unit Kerja] FROM [Unit Kerja Peserta] ORDER BY [ID Unit Kerja], [Nama Unit Kerja]; FROM [Peserta...

The error is not on the form, it's in your table. The row source on the lookup tab of that field is invalid. For one thing, there's a stray semi-colon before first FROM. Not many of us use that lookup field feature: http://access.mvps.org/access/lookupfields.htm Edit: Sorry, second FROM.

Welcome John!

Read the first sentence of my post again.

You would need to use the update events of the 2 controls that feed the calculation. As you've found, the update event of the control with the calculation doesn't fire.

Welcome aboard Ricardo!

Welcome Andy!

Welcome Heide!

Completely agree. A Tesla in our area in self-driving mode failed to merge out of a lane that was ending. Drove up on the curb and had a close encounter with a pole. Never slowed down or swerved.

My first thought isn't code, it's a query against a table with the 36 values, getting a Cartesian product. A quick example using a table with the 24 hours: SELECT tblHours.StartHour, tblHours_1.StartHour FROM tblHours, tblHours AS tblHours_1 This produced the expected 576 records.