Search results

Perhaps screenshots showing the problem would be helpful. Thank you.

Damned if you do, damned if you don't. :rolleyes:

I think the whole Lookup field thing with value, or descriptive, fields being displayed rather than the actual Foreign Key value, makes for potential confusion. I wish SP lists had a better option. In PowerApps, there is some additional difficulty using Lookup fields, as you note, because of...

Thanks for adding to the SSMA GitHub for this issue. https://github.com/microsoft/SSMA/issues/20

While it's certainly true that you can enforce RI in a PA interface or an Access interface or in PowerBI, I think it makes more sense to employ the table level mechanism that positively does so-- i.e. Lookups between lists. I don't see it as a matter of entering or displaying data directly in...

This is what has been called a "frustrated outer join", a term I find amusing and apt. Change the join to a Left Outer Join, showing all records from tblConcernFormSubmissions and only matching records from tblPlaceConcALL. Add as a criteria: tblPlaceConcALL.ConcernID Is Null That will return...

Perhaps the problem is the reference to lookup fields in different contexts. In the Junction table called Issue_WorkArea, you have two foreign key fields: lkpWorkAreaID and lkpIssueID. Both lkpWorkAreaID and lkpIssueID need to be Lookup Fields in the SharePoint list/table. That is the way to...

I agree, yes. Once the tables are migrated, building the Access interface is largely the same except for the meta data fields added in SharePoint which you don't need to include in Access forms, etc. I just ignore them.

That would appear to be correct, yes. The Lookups in SharePoint should include only the respective Primary Key fields, with no additional value fields being needed. "I'm thinking of migrating from the lookup field to lists using sql and vba. Thoughts?" I'm not sure what this would entail. If...

The most basic question of all is this: "Given the design requirements specified for this database application, does it meet all of those requirements satisfactorily." Since we can't see those requirements and can't see the database application itself, it's impossible to evaluate it...

Wondering if AI fits your Access development work? Get some insights from John W. Colby, who shared his successes (and a few frustrations). AP: Leveraging ChatGPT for Incremental Development in Microsoft Access

I started a request early Saturday, the 9th. ChatGPT 5.0 promised to complete it but offered no timeline. After 2+ hours I asked for a progress report. It replied along the lines of "I'm working on it." Over the next two days, I got a variety of firm deadlines, (2-4 hours, 4:00pm, and others)...

I agree, but the way I see it is that PowerApps and Power BI fit in where Access is not the strongest, i.e. remote data entry and data visualization. It's not three co-equal apps overlapping each other. It is finding the best fitting app for a specific kind of requirement and creating a hybrid...

I didn't plan them in any specific order because it's not oriented around a build process. I guess just sequential from oldest to newest for the Northwind series would be a good approach. The older videos refer to a library application I created a few years ago. It does more or less track the...

My primary use has been for Stored Procedures in SQL Server.

I should have noted that I find the form factor for a smart phone makes PowerApps sketchy, albeit possible. I've settled on a cellular-enabled tablet as the better choice. Maybe the 20-somethings with perfect eyesight can find stuff on a phone, and there are thousands of apps for phones. I guess...

Yes, use Lookup Fields where you would, in Access, add number fields for the Foreign Keys to the two parent tables and enforce RI. The Lookups should probably include only the required Primary Key field, no display fields, as is usually done in Lookups. For some use cases, PowerApps makes...

I arrive in Seattle in 1980. Different place now. 😆 I moved to Puyallup a year ago. Love it here.

Yes, that's why I was being nitpicky. It refers to someone in that SharePoint tenant. If it is a required field, and I think that's optional, then that might account for the error.

Or did you mean "Person or Group"? Or something else? SharePoint is a different environment.