From: john via vb-access-l [mailto:vb-access-l Groups. From: Ted via vb-access-l [mailto:vb-access-l Groups. This brings up the Properties sic dialog and you can enter a description of the query here. I realize Access emphasizes the QBE but was wanting to explain why some things within some queries were done a certain way. From: Martin Walke via vb-access-l [mailto:vb-access-l Groups. This brings up the Properties sic dialog and you can enter a description of the query.
And why would you want to comment your queries anyway? From: Michael Meyers-Jouan via vb-access-l [mailto:vb-access-l Groups.
The comment s would not be unseen, in fact that is the goal to have the comments seen when in SQL view. From: Mishe via vb-access-l [mailto:vb-access-l Groups. It would, if you put it in the select statement with a field name. But, only putting it in the where clause gets around that. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Since the creation of SQL in the early s, several proprietary adaptations have been formulated.
Microsoft Access uses a version of SQL that is very close to the original, definitive language. Visual Basic went through a transformation in when it was integrated into the. NET framework. For a while, it was called Visual Basic. NET or VB. NET but now has gone back to the Visual Basic name. Visual Basic is still supported by Microsoft and is still being developed.
The latest version is Visual Basic , which is also referred to as VB This is sold as part of the Visual Studio package.
This is not included in G-Suite. The current status is that Microsoft is fully committed to continuing development and support of Microsoft Access. Access could have been the premier development platform for small to medium size applications but Microsoft completely blew it!
Have the ability to create a standalone executable application. Have the ability to convert an application to a web interface. Get rid of the stupid ribbon and have more flexibility in developing the UI.
Agree with you? MS showed a lack of vision on what Acceess could have been. They have hust ceded cloud based db app territory to others. An enjoyable read. The truth is that Access has no rivals. This is a shame because there are some problems with it. The other problem is Access gets a bit messy for big projects. If you split it into separate modules that helps but then you have multiple copies of your library code or at least on Access I had that problem.
The only reason why everyone is using Access is Office dependency. Not Access dependency. Office, as well as Windows. This two dependencies are not to take lightly, particularly in the developing countries. Access has proven to provide us the best overall value for many years.
We can easily create and manage small applications with no assistance from IT. Microsoft will continue to support it indefinitely. There are way too many Microsoft Access applications in production-critical business areas to simply pull the plug. I am just a dumb redneck from MO who was fortunate enough to get exposed to MS Access nearly 20 years ago.
During the last two decades, I have been able to develop many applications to manage data, and give users functionality that they would not otherwise have thanks to MS Access. While all of the things I have been able to do with MS Access are possible through other means, it seems like finding developers in the workplace who will make these things a reality are few and far between.
I listen to people in I. There solutions are SharePoint forms that are very simplistic and limited compared to what you can do with MS Access. Yes, I can create a SharePoint form on the Intranet in minutes for someone to add data to a table. However, giving someone options that are molded to their specific working environment is not an option with those forms. My databases that I have designed over the years with MS Access are applications first and databases second.
I have designed everything from a simple personal contacts database to a custom form that allows the workers in my field of work to make phone calls from an Access form that queries contacts from multiple data sources.
I work as a power grid operator who has to call people out when power outages occur in a timely manner. The user then selects the first name in the list and clicks a call button on the form. A phone call is initiated with the calling software our phones use dialing the number selected from the list in the Access form. The reason for someone to say that MS Access is irrelevant, when it can perform a custom workplace function like the one I have given in this example, can only be explained by one reason — the people making that statement do not know how to use MS Access to its full potential.
I have done many things with MS Access over the years that have made places I have worked more productive. People are mesmerized by some of the tools I have created for them with MS Access. We have an Outages Calendar that we manage with a SharePoint form on our Intranet, and I used Access to tap the data in that calendar and place the data in a custom form that displays a full screen view on large monitors in our work area with the upcoming work we are expecting on our power grid.
The form also has a feature that allows us to toggle between that screen and a full screen view of the weather radar on these large monitors for defined time intervals. We have some really cool tools that many people see when touring our facility. They have no idea that a software that is part of the MS Office Suite is what is making major parts of our operation click. Even with some of the custom applications I have been fortunate enough to design with MS Access, I have only used a minimal amount of its full potential.
If it can make it until April , I will be one happy man. Hi Chris! I have also creating many applications for our agency. You name it, I developed it in Access. I LOVE the app and the apps are all so dependable. I was wondering if you encountered the last release. They somehow broke control of the. It broke the ability for multiple users to open. First one in locks it exclusively.
We had to revert back to. SOOooo frustrating. Maybe I should convert all my backends to SQL but I love the ease and flexibity of just linking to an Access data file. So nice to see another developer out there like me who sees the intrinsic value of Access. Many in our IT staff demonize this app and are also completely ignorant of how it even works. Take care, Kennedy. I was stuck with simple librarys for storing tables in files. A full relational database, more so than FoxPro.
Proper SQL queries. For the sorts of things people do in business there never was anything better and after 30 years still nothing better. I keep looking. The only rival where I was working was Lotus Notes.
The secretary could generate a database and send out a form by email and have answers typed directly into her database. It took her about 10 minutes to do that. I really could not do that in Access. Obviously IBM killed that product it was cutting their bespoke programming profits. The only other way of getting the same result as Access would be to use an Integrated Development Environment and code it all up in a compiled programming language.
You get a better result but it would take 10 times as long. So arrogant to drop Microsoft Access, i have been a supporter since Access2, Using large amounts of VBA and automation some bespoke programs can be created, totally not available off the shelf, and a far cry from a contact database. Standalone databases not on the web still have a place in business. Keep Access going we have made you a fortune over the years. We used Access in the same way for many years, but moved away from it, favoring SQL scripts over GUI-based operations because scripts allow better repeatability, modifiability, QA-ability, self-documentation, and version control.
I expect to see it in future antique shops and museums much like the toys from my youth are now displayed…. Google Forms for what I catch is a single table form presentation for a spreadsheet, by nothing a database handling and linking different tables. The only real downside to MS Access is that it cannot be effectively deployed via a browser. This limits internet access to an Access application to a virtual Windows desktop environment like a VM or Citrix.
Access is a great front-end GUI and report-writing solution for small to medium companies as well as departmental apps. The new direction of Microsoft to the Power platform is great and Access can to some degree work within that framework. Over the past two years I have been developing a robust data modeling and administrative system that integrates across numerous functions and applications. It uses Access a conduit for data transformation and publishing.
I completely agree with you Phil, and to add, I think that MS Access has become one of the most underestimated tools over the past few years. Where I live almost every medium sized company and quite a few large companies have moved over to O and are beginning to take advantage of SharePoint, PowerApps and Flow. I always create my relationship based tables in Access and then upload to SharePoint. This gives me the ability create a fully relationship based data-sets in SharePoint within minutes.
And as you mentioned, the mere act of opening Access with an internet connection automatically backs up the data and also gives users the ability to perform offline tasks… Amazing!
It is imperative that MS Access is supported for Microsoft NET6 on VS, as the demand for such developers is growing day by day and we will be able to use Access skill for next 10 years.
It is easy to link to multiple Excel or. CVS files and do regular, right and left joins using Access. If there is a cheap or free tool that does it as well and easily, would love to know about it, but until I find a replacement, for this tool alone, I would truly miss it if it were gone! The article completely ignores the online support angle. The level of crowd-sourced support is just astounding. You Google the problem and get nothing. Oh, and the fact that Access has changed so little over the years?
It means that the subroutine you find online from will work today. Same with the instructional videos. Makes you realise in the end these new features are just not worth spending the time learning. Show me any other product out there where you can develop complex DB application from analysis to deployment in less 15 minutes. I do hate it, but will miss it if Microsoft nix it. I am sometimes amazed that some of these databases even work when I see how badly the tables are designed, and the associated VBA, queries etc.
Access is unique, because it is a database that comes with a full set of tools to build a functional application. Or you could call it an application builder, that comes with a database! There are many of these legacy applications running well under current versions of Windows and many clients who would be lost without them.
They have a very large customer base that depends on it. One thing about Access that many developers love: it has a small footprint and is highly efficient. New highly specialized applications can be developed quickly and relatively cheaply. The downside with Access is security, but when it is deployed on a network, network security takes over and these applications run securely. Access rocks. The ribbon sucks.
Microsoft totally blew it with the later versions that it developed. Access could have evolved into an extremely powerful tool for small to midsize applications using SQL Server as its database. I used to work for a company that was developing applications in dot net using C sharp. I am still clinging to Office for that same reason. At work I use Access desktop version to store and combine data from different sources f. To me, storing data in Excel is like summoning the evil one.
MS query in Excel is painfully slow and data integrity… number stored as text, oh my! Access does all that, the query builder is terrific, and you can build and automate reports in no time. You have no idea how much time I save with reporting only.
Btw, try sharing data with an external company via Sharepoint, Teams, Onedrive if your global sysadmin acts like Mordac, the preventor of information services.
Mail an Access report or exported query and everybody is happy. Hello there! One thing Assess in not that good is a security. And this is not discussed in length or not even mentioned. Security this days is a paramount and no matter how much Access is good as a tool, it is not safe for anything more than a home usage. Yes, the SQL Server can be used, but than it is not a standalone database, and multiple licenses are needed.
Still, one can connect and dump the data which is exactly against the security principles. So, decisions, decision, is Access for domestic usage or corporate? I am getting daily questions on how to move Access to the Web. The interest is huge. I contributed to the invention of Information Engineering.
I have experience. I started using Access version 1 in and was impressed by how easy it was to use. I developed the SQL Server back-ends, wrote the stored procedures, etc. Why not split the query up into several other queries with descriptive names?
Can you post the SQL? Thanks Norie, I was afraid of that! I appreciate the point about splitting the code up with better names etc. I will not send sample code because it was more a general query. Thanks again. Joined Apr 30, Messages 1, Just how are you saving your SQL statements? Do you stash them into a table and extract them from there central point of reference? Do you build the SQL from code querydef? Or do you build the SQL and just use them, referenced by name. Hi Mike , I am not sure I full understand the question but here is my reponse.
I use access I save my query by simple closing the window with the SQL in it. My SQL is generally no longer that 10? Hope I am making sense! Select properties and type something into the box that appears. Instant "comment" visible only in the window display. The questions were based on different more technically complex techniques. Basically, instead of maintaining unique query objects, add the text of the SQL statement into a field in a table.
Then, open that table and extract the information, dynamically build the query and use it. Aka, it never resides under that query tab. Gates Is Antichrist Well-known Member. Joined Aug 15, Messages 1, That is a great approach. I use the "property" comment field heavily but I like your sophisticated angle. If his queries are becoming extensive, they might possibly be maintained more succinctly in code and, hey, with the bonus of unlimited commenting there, no less.
Thank you all!
0コメント