Search results

Yes, but why are you doing it? What benefit to you is obfuscating this code, especially as it's likely mainly based off publicly available code scraped by an ai?

Try the following queries in the query builder to see if they produce different results: SELECT t.TransactionID, t.fAccountID, t.AccountName, t.CkDate, n.FullName, t.Cleared, t.Debit, t.Credit FROM qryCkTransaction t LEFT JOIN tblNames n ON n.NameID = t.fNameID WHERE...

Are you sure this doesn't work? You should see only: transactions from account = 47 uncleared transactions from any time both cleared and uncleared transactions within the date range. Do you have any other criteria? What is your whole SQL in the end?

What is the benefit of this obfuscation?

You really should be able to glean this info just using a query. Please describe the tables/queries (table names, field names, datatypes) used in main form and subform and which field relates them.

Love the way your keyboard is upside down! 😝

Removing the blWrap clause loses you a major part of the function's utility: removing the necessity to fiddle around adding # delimiters in your SQL. If you had copied the code I had posted and replaced your equivalent code you would not have ended up with doubled delimiters. Notice I removed...

Since this date is unambiguous, it will be parsed in SQL correctly as 28th Feb, But not so with "11/02/2024" - that will be interpreted as 2nd Nov. Indulge me. Add a function in a standard module: Function SQLDate( _ vIn As Variant, _ Optional blWrap As Boolean = True, _...

No, it's not. It's in SQL date format so it's "mm/dd/yyyy" Dates passed to SQL must be in either US date format or an unambiguous date format like ISO: "yyyy-mm-dd" How are you constructing your filter? Please post the code you use.

Do you have a space between the greater than symbol and the equals sign? If so, I suggest you remove it.

Yes, I guess I was aiming more for something like: SELECT [Q] & ": " & GetRSPUnderscore ([a]) AS QandA, [Q] & ": " & Trim(Replace(String(Len([a]), "_"), "_", "_ ")) AS Demo FROM Table1; so as to have just a single underscore per actual letter, and your solution gives that option. (y)...

That'll teach me not to check the docs! Have been writing you'll much js/ts and confusing with string.repeat() 🤪

:ROFLMAO:

Surely just a small adjustment required: SELECT [Q] & ": " & GetRSPUnderscore ([a]) AS QandA, [Q] & ": " & Trim(String(Len([a]), "_ ")) AS Demo FROM Table1; (nb untested 😬 )

Colin did try and explain that to you in Post #85 (y)

You can do it with a pure query, without a VBA function - see this post (and thread).

Are you plotting inter-planetary flight paths? :ROFLMAO: That's a lot of scale for such large numbers! I'm not sure how you go about it. As explained, DECLARE @e1 AS DECIMAL (28,16) = 1, @e2 AS DECIMAL (28,16) = 1.95; -- is the same as: DECLARE @e1...

From the docs: BEGIN DECLARE @e1 AS DECIMAL (28,16) = 1, @e2 AS DECIMAL (28,16) = 1.95; -- ... 28+16 = 44 44 > 38 This could likely be the cause. See Philipp's second code suggestion in Post #15 (NoMoreWTF) Your result is the same as DECIMAL(28,10) - try that and...

What about the vbCr here? (Chr(13))