Search results

Here is another approach that I have been using for years. I find it very intuitive, easy to use, and mirrors how you do things in Access. I am not disagreeing with Marks approach, but that is not how I would do it. The concept of the strategy makes sense to decouple the processing from...

The lookup and multivalue fields where needed by Sharepoint because of limitations in not having any real forms. You simply had a list. Now a lot of people are doing their data entry with PA and data visualization with Power BI and only using SP as the repository. If you are not reliant on SP...

In SP you can create a lookup field and allow it to pick and store one choice, or you can have it store multiple choices. Using a multi value lookup it will show multiple choices in a column. So you would have an issue and a column with 1 or more worktypes. Again that is only display and not...

If I was not using traditional Sharepoint as the interface for entry and viewing then I would go with 3 and simply store numeric keys. But how do you plan to display the Many to Many in Sharepoint? If you are not then OK. I am more a consumer of PA then a builder, but I would assume you would...

The three choices would depend on where you are doing the bulkof the data entry, editing, and visualization. If you are doing everything in Access then go with 3. You will have to enforce RI at the form level. If you are doing data entry and visualization in SP then go with 1. If you want a...

Have you read this because I will argue you can do this with multi select lookups (MVFs) or do it more traditional and still get the same capability. Although it may make your head spin using MVF lookups. However, you will need to understand what is going on in the background, because what you...

My point is that I doubt any of the lagging has to do with identifying and moving to the "new" correct record. So you have to do some other troubleshooting. I would see what happens if you test it without CF. You cannot upload a video unless you zip it as a file. To display you need to host it...

George beat me, but I think we are saying the same thing.

Not sure what that means. Issue_WorkArea is a list but acts exactly like a junction table in Access If you use a lookup field in your new the list Issue_WorkArea, when you pick an Issue description it saves the Issue ID even if you thing you are picking a descriptive field. If you pick a...

This is likely having to do with conditional formatting, I doubt there is a code issue. My solution works regardless of how you sort or filter the datasheet.

Works for me I think. Option Compare Database Option Explicit Private CurrentID As Long Private nextID As Long Private FirstRecord As Boolean Private LastRecord As Boolean Private Sub Form_Current() Me.txtLink = Me.OrderID ' for formatting End Sub Public Function LaunchDetails()...

I think I could get my head spinning trying to move the postion. I think I would add these properties to my form IsFirstRecord ' boolean IsLastRecord 'boolean CurrentID ' PreviousID ' ID of previous reocord or something like 0 is you are at first record FollowingID. ' ID of next record or...

https://www.access-programmers.co.uk/forums/threads/prevent-ms-access-to-autosave-data.325707/post-1854876

That is where we are going in our company. We use SP but mostly as a data repository and navigation tool. A lot of the entry and edit is a custom Power App. Instead of views we use a lot of BI for viewing the data. This way the user is not touching a live list. I do not know if that is your...

I bet People displays a person name, but it is pulling data from the exchange server so I bet it is actually storing some kind of exchange ID. So I would think it is a kind of lookup field.

Here is another example. You say you have nine tabs now. But maybe this could grow to 15, or 20. If that is the case you can add 20 tabs now and then configure the ones you use at runtime. It could pull this data from a table. In this example a law firm has a different number of partners...

I would try testing it field by field. See if you can just add the title. If that works add another field. If that fails try adding a different field. I would think this would work even with a lookup in the table. I will tell you the default fields "Title" and "Description" always seem to...

I have the subform hanging over the tab so you can see what is going on. If you make the tab wider then it appears on the tab.

You can take a subform and put it in front of the tab, not on a page in the tab. It will look like it is on the page, but since it is in front it will seem as if it is on all pages. Then when you change the tab control all you are really doing is modifying the source object. The other way is...

Yes you should have one and only one form. In fact I would go further and say you only have one subform too. What is the parameter? is is a filter?