Search results

maybe to help debug add some print out On Error GoTo 0 Exit Sub Test_Error: Dim strMsg As String strMsg = "Error " & Err.Number & " (" & Err.Description & ") in procedure Test, line " & Erl & "." strMsg = strMsg & vbCrLf & " Topo Path File: " & strTopoPathFile strMsg =...

The JKP Treeview builds a tree dynamically from a Userform and MSForms controls. This is the best example of what you could do with a UserForm and cannot do in an Access form. See discussion...

In Access you can actually use two types of forms. The Access form and the VBA UserForm. If you make Excel applications you may be familiar with UserForms. 1. Need to add the toolbar 2. Now you should see it in the insert menu 3. There are some different things you can do with a Userform...

Not me, but here. https://www.access-programmers.co.uk/forums/threads/scramble-text.308060/

I am with Pat, this is such an overly engineered approach to do a trivial task in Access. If you did it using Access and not working around it. If you want to go this route and you are experienced in .net then you are much better off building it in .net as the front end and using either your...

Chatty is never wrong.;)

Wish I would have seen this earlier. I have a few pretty large command bars. Here is one example https://www.access-programmers.co.uk/forums/threads/access-item-genie-demo-for-organizing-tracking-your-items.333517/ It started small but I kept adding buttons. The code really became a pain to...

Never done it but according to Chat only the display name changes and it is still called ID. My guess if you link to Access you will see ID and not the new name. And it seems you need to remember it is really called ID when using Power Apps. My guess ID is what you are going to see as a choice...

I will give a little more context In other languages you have what is known as Static properties and Procedures. This allows you to build a class and encapsulate and protect the functionality, but utilize the procedures without having to instantiate an instance. Example in VB is the Math class...

Using @isladogs code you can find more than in the code. Especially row sources of controls. The code would need to loop the controls too, which is not currently included. The query provides a lot of info Determine if it is a form, report, or control that uses it in a query. Knowing where the...

To launch from code Public Function OpenZoomBox() DoCmd.RunCommand acCmdZoomBox End Function Now you can put this in most controls with a double click Select all your controls that do not have an event handler already. Then in the On Dbl Click property =OpenZoomBox Then you do not have to...

One thing that may be an issue is the available font

Update us if you have success in doing this with PA. I would be interested in what you learned.

Sounds like a bug dealing with the specific screen resolution. In the mean time they can try the built in zoom to enter data shift f2 Or you can build your own custom zoom box https://www.access-programmers.co.uk/forums/threads/how-to-make-record-cell-expandable-for-words.314148/post-1723877

FYI you can change the ID column name, but I would not recommend it. So unlike in access I would never have all my PKs named ID. I give them a unique. Here is how and why I would not change the name.

That is what I thought. Complex column is an attachment, mulitvalue field, and memo history. In SP I think a lookup is also a complex data type where in access I think it is just a display thing. But this goes to my point about a name that does not reflect what it really is. You showed it...

If there is data in the lookup tables then do an insert query into the new columns. If there are no existing records simply delete the old columns and create new ones. Never change the datatype of a complex column, that will cause issues.

I do not think Mark and I were necessarily focused on solving your specific problem, but more on demonstrating coding concepts and techniques that you and others can use anywhere. Mark identifies some general design concepts that you should strive for I may have approached this differently, but...

I would not change the data type. I would create 2 new fields. This is like changing an autonumber field in Access you will get issues.

I just ask that in your junction list, if you are not using a lookup, that you get rid of the "lkp" prefix for those column names. That will confuse most anyone who is looking at this. It is like when someone drops some code and they have some thing like txtBoxABC.rowsource = ... Then I look...