Recent content by MarkK

If you don't like this design-time behavior you can load your subforms/subreports programmatically. • Delete the name of the form you want to load from the Subform.SourceObject property in design view. • After the main form opens--and even on a timer if you want more delay--do...

I was chatting with AI about love. It posed this question... When you imagine acting out of love in a hard situation — confrontation, departure, sacrifice — does it feel like expansion or contraction in your body? Like wtf?!?! How does a machine, in an abstract conversation, generate that?

Anything humans create incurs a cost to produce and distribute. This being the case, an interesting question to consider in respect to any story/claim/assertion is... • Who will profit from it? This is a 'follow the money' trope, and exposes dynamics far more nuanced than a true/false or...

I think the scope of your question is broad, and may in many cases require book-length response. But yes, I have successfully submitted questions to AI via HTTP and received valuable responses. It's possible a PowerAutomate Flow might offer you some kind of generic wrapper for specific...

Are you sure? This causes an 'overflow' on my machine (because 2 ^ 15 exceeds Integer).... Me.Text0.Width = 2 ^ 15 This causes 'The control or subform control is too large for this location' (because the form isn't that big) Me.Text0.Width = 2 ^ 15 - 1 What I run into most is setting...

How have you tried using DateValue()? This sounds like the result you would get if the date values in the table do not include times. What are the table values in the date_of_change field for #4/12/24#? Try this in the immediate pane... ? cdbl(#4/12/24#) Then try this... ? cdbl(#4/12/24...

Most MS Access control location/dimension properties (Left, Top, Width, Height) are typed as Integer and represent Twips. • The max Integer is 2 ^ 15 -1, or 32767. • There are 1440 per inch. Doing the math, 32767 / 1440 = 22.755 inches. Lots of modern monitors are way bigger than that. It's...

If you have a ProcessA that consumes a subset of rows from a larger table, and you have query qrySubsetA that correctly returns those rows... It is a make-work project to... • Drop tblSubsetA • Create tblSubsetA = qrySubsetA • Execute ProcessA with tblSubsetA It would far simpler to... •...

I don't think you can express idealism in practical terms. In practical terms, the US is in trouble. Have you seen tape of the current head of the DOJ in front of congress? OMG! • Implementing ideals requires respect, first of all for your colleagues, and then of course, for the ideals...

OMG! You're so... idealistic! : )

I agree. A 'category' must be a squishy UX distinction.

If you experience AI as sweet-talking you, ask harder questions. If you ask AI to validate your process, it will, even if that process has glaring deficiencies. I increasing ask AI how my process sucks, and how it's likely to fail. AI is like a mirror.

And with a single table you can omit the table name, like.. SELECT DISTINCT Name FROM MSysObjects WHERE ParentId = -2147483645 AND Not (Name Like '*Sub*') ORDER BY Name;

I think this is true from a purist perspective, but it's convenient to just sum a single field as opposed to summing credits, summing debits, and then summing the sums. But it is proper accounting to have debit and credit accounts, and to post debits or credits independently.

I once asked an AI why it sucks so bad at VBA, and it explained that VBA is wrapped in a file type that requires opening an application, so it has (and it stressed this point) far fewer code examples to consult.