Search results

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...

Ahh... No. All you are showing is a bunch of hard wired events procedures. So what? Not even related. The point was to handle of multiple events without writing multiple Event Procedure. More apples and oranges. Now I am confused why Dalski would give you a thumbs up, because I cannot see...

You will have to pull the thread on that one for me because I am not seeing it. The OP wants to trap the right click on a mouse down/up for multiple controls. This one is complicated because the event procedure requires parameters to be passed from the application Private Sub...

I assume you question is can you apply some settings to control what the wizard does. Probably not easily. The wizard uses a complex formula based on field data type, field size (i.e short text 10 vs short text 255), page width, printer settings. Does its best guess to make it close. The only...

So now you got me kind of leaning back the other direction. I have experience using simple numerics and ensuring the data integrity at the form level. I know that works without any issues. It is all these downstream limitations of a lookup field, I do not know.

That is kind of my thought, but sometimes I just do not know what additional baggage the Lookup field brings. I have started from the other direction and had a working access database that I moved the BE to SP. Because I had the data already I did not want to change all the foreign keys to...

I am sorry but this is 10 times funnier, because it is two completely unrelated topics. This is such a complete "apples and oranges" comparison that it makes no sense at all. Have you not been following the conversation? Explain again how the tag property will replace the capability of a...

Here is what the right click would look like. Form Private WithEvents RCTBs As RightClickTextBoxes Private Sub Form_Load() Dim ctrl As Access.Control Set RCTBs = New RightClickTextBoxes For Each ctrl In Me.Controls If ctrl.Tag = "RC" Then RCTBs.Add ctrl Next ctrl 'MsgBox...