Sure, MS has Windows 8 tablets, but no one WANTS WINDOWS 8! ANd we developers don't want to abandon $50k OF TRAINING TO LEARN A NEW WAY OF DOING THINGS THAT IS TOTALLY NOT THE WAY WE WANT TO DO THINGS!ĭone ranting.
When Windows 7 is no longer available to them, companies are looking into Linux, and individual users are finding Android tablets to be a goodĪlternative. It's been out for over two years, and most users are sticking with Windows 7. AND, do not expect to get thatīeing a total capitalist, I am fine with this attitude, because the fact is, if MS keeps with it, they will find their products less accepted by users.įorcing WIndows 8 is a good example. One thing that annoys me as a developer is MS' attitude of, "Yep, we took that away.
I have been using Microsoft tools for software solutions since I learned QBASIC, over 20 years ago. If any one knows if it is acheivable to create a 'floating' form and load a custom ribbon I would dearly love to know the secret and you have my thanks in advance. Ribbon is if I set popup to no and then the form returns to the top left corner of my screen. The only way I can get it to load the custom You see I just want a clean looking form, I will put all the options that I need on my form and although you cannot select anything from the ribbon because the form is modal it still puts it on the screen. If so, the unbound option is the one.I am trying to create a 'floating' form, by that I mean a form that does not look as if it is docked and does not have a bookmark tab, and the only way that I can do it is if I set the following propertiesīut when I set these properties Access does not allow me to load a custom ribbon - even if there are no controls in the ribbon and the xml is as follows: The other key decision point for me if your Microsoft Access database will be shared and more than one user could end sharing the same form (and even record) at the same causing potential record locking and conflicts. To gain the overall control of a form and its controls (which can also be unbound), you use the unbound approach ending up with a more professional and polished interface. It would take tens of thousands of bound records with poor indexing to start to see a difference.
One of the main questions (if you are comfortable with either approach) is will it provide better overall performance if you choose the unbound option? The quick answer is "not necessarily," as a bound form with less than a 1,000 records and certainly wrapped via a query will be very quick indeed. That’s the answer here for me and the link to a previous article demonstrates some of the pros and cons for you to evaluate the best route.
The key point to help answer if we should use unbound forms is of a personal one and whether you, the developer, programmer, or "power-user," have the time and knowledge to add some VBA code to help support the unbound approach. Microsoft Access Database Forms: Should We Use Unbound Forms? One property we are talking about of course is the "Record Source" property (from the main form design area), which is where you either set a data source (table, query, or SQL statement), binding your form, or leave it blank, making it unbound. Microsoft Access, like any other development IDE, will provide an endless set of properties across the "one-stop shop" set of objects and forms are no different. a bound Microsoft Access form is will help divide the distinction and allow you to determine which approach will suit best. Plus, I like building things.Īs a recap, knowing the difference between what an unbound vs. I’ve always been a big fan of Microsoft Access VBA programming why? Because I like the way a rich application like this can be customized and designed from the floor up with little IT programming and development knowledge.