Search results

Maybe your app can update a server table at startup time, and again every 5 minutes, to say "I'm here, this is my name, and I am connected.".

ProductIDProduct NameUnit Price 1Chai$18.00 2Syrup$10.00 3Cajun Seasoning$22.00 4Olive Oil$21.35 5Boysenberry Spread$25.00 6Dried Pears$30.00 This works: first paste the query into Excel worksheet, then copy to clipboard and paste here.

KitaYama apparently knows how to do it: https://www.access-programmers.co.uk/forums/threads/this-sql-problem-is-the-max-amount-of-frustration-i-can-handle-right-now.335021/post-1983269

Maybe this can happen if twinBASIC would pursue integration with Access. It's currently not on the 12-month roadmap though.

Peter Cole has an auto-converter.

MzTools has a pretty nice one; fully configurable. Best 100 bucks I ever spent. ' ---------------------------------------------------------------- ' Procedure Name: $P[CODE_ELEMENT_NAME] ' Purpose: $U[Procedure Purpose] ' Procedure Kind: $P[CODE_ELEMENT_KIND_DESCRIPTION] ' Procedure Access...

Are you sure it's an empty string? They are hard to distinguish visually from a Null value. But this always works: Put the cursor in that field. In the Immediate window (Ctrl+G) write: ?Screen.ActiveControl = "" False ?IsNull(Screen.ActiveControl) True To fix the query, you can wrap with the Nz...

You probably meant: in the PROCEDURE that raised the error. That is the scope where it happened.

I responded to "I would think I can encrypt the tables also". I thought that might mean (if Northwind) Customers, Orders, Purchase Orders, and other user-entered data. If encryption is solely to preserve your intellectual property and desire to have people pay for licenses, that is much more...

Re encrypting the data: I am not a lawyer, but keep in mind that holding back user data is a crime in some jurisdictions. Ensuring only paid users are using your app is an issue well beyond the count of Users in SQL Server. You may want to open a separate thread to discuss it further.

If client has full access to the server, you cannot keep them from gaining full access to the database: https://www.sqlshack.com/recover-lost-sa-password/ However, you can encrypt stored procedures, essentially locking up your intellectual property...

We have another report with the same issue here.

I am on A365-32 MEC v2510 and I also get the error with the heterogeneous query. The only way I can make it work is to attach the table from test2.accdb. I realize that would be a massive change to the OP's app, and may not be practical.

I think you're now in the "collect more information" phase. Apparently, it works sometimes on some machines. What do they have in common? Soon this may be seen at customer sites too, so it is an urgent issue. Note that MSFT can turn features on and off remotely, so "no changes were made" does...

I speculate that this is a security issue that was "fixed". You may have to fall back to what most people would do: attach the linked table and create the query that way. No IN clause. Surely that still works?

Is E:\ a trusted location as I requested?

At this point I am not convinced that there is a bug. The OP should simplify the problem, and on the failing machine create two new databases with simple names (without any spaces or other funny characters) and put them in a Trusted Location that also is a simple path, and create 2 simple...

It does not happen on my Monthly Enterprise Version v2510. I'm asking another tester to try it on his more aggressive versions.

What is the current version and bitness of Access you are on? What is the previous version where it worked fine?

> Application.SendKeys "%DA" This assumes you are in the VBA editor main window. Sendkeys is always very fragile, but it may be your only resort since there is no programmatic access to the Watch window.