Recent content by Edgar_

Ken, your alternative in post #15 is not the point, my suggestion is to avoid parent insertion in the same moment you're adding children, regardless of where the user selects a parent. - The OP has not replied in days, and it's a new user, might never come back - The requirement is clear, but...

Hmm... OP says this And you say this: It's not about forcing records, Ken, but the opposite, it's about cancelling records with no problem. From a user-experience point of view, after testing your suggestions, that type of solution is incredibly annoying. When a user tries to cancel an...

Hardware: use the best that exists OS: Windows 11, you don't want to use an outdated OS Configuration: Only the Access install and Windows 11 Add SQL Server and the ODBC Driver to the configuration. Access will use as many system resources as the processor can allocate to it. When your CPU has...

Save yourself from a lot of headaches and: 1. Create a continuous form that displays all the parents. This form is where you will add parent records. Do not add child records in this form. 2. Create a separate continuous form for adding child records. You can only access this form by selecting...

PMFJI, the websocket solution does not care at all about any of these supposed problems, it only cares about who is connected to the websocket, and whoever is connected, it will receive the message. You can then choose what to do with the message by using the event in code in any way you want...

Think of it like a group chat. PC1 says hello, PC2 and PC3 see it because they are connected to the same chat window. A chat service is a Websocket too. The 3 workstations must have a web browser control connected to the same websocket. And on message, all workstations react at the same time...

Not sure Application.Quit will run after you've chosen to close the workbook, so simply quit the application, I think you've already chosen to ignore changes by using the Saved=True property. Sub QuitExcelNow() If Application.Workbooks.Count > 1 Then ThisWorkbook.Saved = True...

Indeed, it's not the same if the record was affected from access, a terminal command, or external client. Identifying the source of the modification is the first step, and it's there where you have to add the code to do additional stuff, if such environment allows it.

Logging into a website from an external browser won't log you in from the edge browser window, they're both different browsers. Opening the default external browser could be done with this: FollowHyperlink "https://www.wikipedia.org" Opening a particular browser, like Edge, to a website could...

Just remember that web browser controls can send notifications through websockets. If the client used to update the record is Access, you can set it up so that this instance of Access sends a message to other clients once the record is updated. Any other Access clients connected to the same...

Traversing all objects is easy, but what you want to do with that is tricky. For example, you can use Application.CurrentProject, then... If it's forms, use AllForms: Sub TraverseForms() Dim f As Object For Each f In Application.CurrentProject.AllForms 'do something with the...

I made a few extra tests and I see that directly executing the query shows the same behavior and I think it's because of the requery method in the context of the after update event. I've never worked with barcode scanners, but I think you'd be much better using the change event + the .text...

I suggest you simply set focus to another control from the main form before you set focus to txtProductCode. Me.sfrmPosLineDetails_Subform.Requery Me.SomeOtherControl.SetFocus ' change the name Me.txtProductCode = Null Me.txtProductCode.SetFocus This might be one of those cases...

Although I've been around for a much shorter time than most of you in more than one way, my interactions with Pat Hartman were always somewhat complicated, even in threads where she was seeking advice. A number of new users expressed similar frustrations, and some even stopped posting, possibly...

No, I meant actually developing for the web browser control making the contents of the control interact with the application.