Search results

My position is that experienced developers who understand how MVFs are designed and how to implement them are more likely to avoid them in favor of more robust approaches. Novices who don't understand normalization, much less the inner workings of MVFs, are more likely to use them and do so...

Simple enough. (y) But with a true Group, it would be: Me.GroupofControlsName.Visible = visibility and no need to poll all of the controls for the presence of the tag.

Same idea, but more code required I would expect.

PowerApps allows you to select a number of controls on a screen and create a group on them. Some properties of the group then apply to objects which are now part of it. One of the most useful I've found it to make the group visible. All of the members of that group are displayed or hidden...

Please elaborate. "...probably the most important thing in a db (normalization) is absent." Are you saying normalization is absent in SQL Server? Or absent in SSMS? Neither is true, of course. But maybe that's not what you meant to imply.

Good point, but I think you took the wrong emphasis. I'm saying that it's more likely a SQL Server DBA would want to work closer to the basic objects, and would, no doubt, be better prepared to do so and would be less likely to consider SSMS inadequate. This discussion is primarily about one...

Let's step back and consider who the primary users are for Access and for SQL Server. Also, let's consider which pool of users is more likely to want a lot of GUI interface assistance regarding tables and table design, and which pool of users is more likely to want to work "closer to the...

Not to be argumentative, but that is a very simple query in Post #2. And it provides an overabundance of information. You can also reference the information in the ER diagram as in Post #3. That said, there's still another way to get a list of Foreign Keys, using TSQL. I got this version from...

The link still doesn't work for me, but that's okay, we can find his YouTube channel and maybe track down the video you mention. Point #3, having worked with both Azure SQL and SQL Server, I can understand the point about user interfaces. SSMS is, at least in my experience, easier to navigate...

My mistake. It was not posted by you.

The link you posted doesn't appear to work. Can you try again? I'm not sure what you mean by "...it's a better management system." Please clarify. Also, could you respond to Tom's question in Post #13? Thank you.

I'm not great at extracting relevant details from a narrative. Perhaps, though, if you provide some sample data for each of the tables described, it would help.

I'm afraid that it would be extremely difficult to help you create an "ideal database" without knowledge of the context and circumstances in which it will be used. We can offer suggestions and guidance, as others have done in the previous 14 or 15 posts. Here are some references to resources...

What problem are you trying to avoid or resolve? Thinking through the process: A record is committed to the one-side table via the main form to which it is bound when you leave that main form. Whatever fields have been populated in that table are saved, but if there are no entries in controls...

I am aware of a couple of Access related websites, one of which is based on Wix, the other WordPress. You can see how successful such implementations can be. I have also created a web app built on Blazor, with the assistance of Claude and Chatty, my AI team. That one isn't yet approved by the...

I would treat it as a normal software development project. Leave the current production application alone, except for required maintenance or bug fixes. Treat the new version as a development application, regularly updating data if necessary for testing as you go. Deploy a test version of the...

Although I also know of no good books on Access/Azure SQL, there are a lot of parallels between hosted instances of SQL Server and Azure SQL. You should find a lot more relevant resources by including SQL Server in your research. The main design consideration, IMO, is that Access FEs with any...

We need more specific details before we can offer specific suggestions. It may well be related to how the subform is linked to the form in which it is embedded. Given the circumstances, providing a copy of the database for review might be the most expeditious way to share the information we...

In addition to the suggestions arnelgp offers, you should consider whether you can implement a Power Automate Flow that reacts to a SQL Server table trigger or other event and sends a notification that Access can receive.

Here's another example of the design pattern for forms to manage many-to-many relationships. It's based on songs and musicians, but the logical structure is similar, as is the interface. https://www.gpcdata.com/downloads/MusicandArtistDemo.zip