Do you sell and Access application?

Our product name is PREMO XPERTS and is used by the process, manufacturing, and power production industries to improve facility performance and optimize their preventive maintenance program. It has been in continuous use at some locations for over fourteen years. We started with MS Access version 1.0 and are currently using version 2002. Clients discover our product via referrals, internet searches, and trade show/conferences. Our three biggest issues are installation, managing end-user licenses, and providing clients with updates. I would like to see MS Access move away from the client-server model and towards browser-based. Yes, I know there are other dev applications that will run in a browser, but too much time and effort are invested in our Access platform. I have many other ideas and suggestions, but don’t want to make this post too long.

My company has several industry specific applications that are sold trough a third party or directly to government agencies. Distributing updates and managing licenses can be challenging. Once the initial application is installed – having the ability to distribute updates, users can install (without administrative privileges or IT assistance), would be beneficial. Also would like the ability to notify users of new versions and definition updates through the custom application by communicating with a secure website. Having the ability to prevent the user from using the application if a critical update needs to be installed would also be a great feature. I have created a simple update utility that checks for updates via IE – however Vista protected mode is preventing its use. Utility located at www.myaccesstips.com/.../webupdater.htmlAV22

The utility link should: www.myaccesstips.com/.../webupdater.html

1) Please, give us some lessons about how to safely install Access applications on machines with different version of Access. I'm sure Access team knows about their BUGGY PDW, which is not able to do anything correct and safe!!!

2) Create a professional install tool, something like Sagekey scripts for Access. I really need one. I have spend my money for Access Developer edition... well, I don't really know why you call it Developer edition if developers can't create easy and safe installation packages. :-( 3) I hope we all get the new installer for free as soon as it's available. Thank you very much in advance.

4) At the moment I'm with A2002. In accordance with A97 it's a real crap - too buggy... and thus no rapdi development.

5) Throw away new A2007 developer's GUI - it's unbelievably complicated and slows down development. See Clint Covingthon's blog: blogs.msdn.com/.../do-you-like-the-new-navigation-pane.aspx

6) FIX OLD BUGS before any other new release of Access. MVPs will tell you stories...

7) And, yes, I need an installer in Czech language...

I'm glad to see you are even thinking about this! #1 Add built in professional grade controls: Treeview, Grid, etc. With the ability to sort, change color or icon by value, etc.

I once did, but I gave it up!! My company had a very comprhensive package for HR (1999), which was filled up with great features and very competitive, when my prospects met the message from Microsoft, that Access was dead. Are you serious this time??? What happended that time was that my prospects totally lost interest. I still have the package and now I have got some interest for it the last two months - your impact on the market is so hugh that you must be very carfeul on how you act! I was burnt!!

Yes, we have a few industry vertical market solutions we have developed that are quite successful. Our key problem areas are also mentioned by others whereby: A) something can work on all of our test machines (abot 20 machines total) and each test machine is setup with different configurations, yet I onstantly run into issus where installs in client enviornments have problems running the solution. Usually a windows update will take care of it. B) the attachment of access to office causes significant problems with an alternate version of access is running C) Other problems have been encountered, but Ive brought these to your attention in various previous posts. Access has a breat potential as a RAD tool if you would start treating it as such vs. a Office Tool. Most office users are not going to versed enough to use Access anyways, and keeping it as part of office doesn't benefit anything. I see it does more damage. I am constantly having users Uninstall Office Professional and selectivly install everything except access just to keep these issues from occuring without production products we send out as complete solutions. Im tired of having to explain to customers WHY they have problems with our software running with microsoft office 2003, but no one elses softwaer has problems. And its always related to having access 2003 loaded alongside access 2007 - This should not be part of microsoft office. Its not an office productivity tool, rather it is an RAD tool used by developers, not end users.

My company offers a Microsoft Access product ("UI Builder for Microsoft Access") that serves as an application framework to help Access developers jump-start their development process by minimizing the need to create common Access functionality like attractive menus, event logging and alerts, Mail Merge, and more. Our Enterprise Edition includes user-level main menus (similar to a Switchboard that is customizable by user). We've built in over 25 different menu commands so that Access users can configure a menu button to do nearly anything they would want, without requiring any VBA experience on their end. People use our application because they want more attractive Switchboard-like menus with more functionality, and they don't have the time or knowledge to build it themselves. In terms of what would help me sell more product, Microsoft's continued support for Microsoft Access, and a solid roadmap for VBA or it's equivalent. Finally, customers purchase the product online (via Office Marketplace or directly through our site). Thanks for asking! www.opengatesw.com/products.aspx

Thank you for this topic!

I read a few sites that try to compare between desktop and Web applications to see which is better. Although you can always say that it depends on the purpose of the application, in general the conclusions were that a desktop WEB ENABLED desktop application will be better because the improved user interface and speed of accessing the data. So how can we “Web Enable” a desktop application? I think deployment of the application and its updates is a critical key issue. The greatest advantage of a Web application is that you don’t need to deploy anything since all that is needed from the user is a browser. If this advantage could be bridged even some, then Access can still rule. I think the Access team should brainstorm in order to find ways to make this process easier for developers and users. I agree with Larry above that the key issues are installation, managing end-user licenses, and alerting and then providing clients with updates, but I do not agree with him on moving away from the client-server model and towards browser-based. That will take away the edge access has over other available platforms, that being the quick and sophisticated user interface. I currently have four applications that I would like to deploy over the internet.

Here is what these applications do:

1) Manage academic journal’s editorial process.

2) Manage the administration of the Dean’s office of academic faculties

3) Manage the administration of Orchestras and Choirs

4) Help people learn new languages. Thanks

Gilad

1) Distributed database for "crossworders" with ~400.000 records & supprt application (filtering, creating various search criteria, ...)

2) Advertising.

3) Desperatelly need a professional installer in Czech language. Your PDW is buggy and I'm experiencing cross-version incompatibility issues.

1) Right now I'm working on a HUGE accounting system.

2) We shall advertise...

3) In this case I REALLY need a professional installer in Czech language. Your PDW is buggy (see above) and I'm experiencing Access cross-version incompatibility issues. We have just released a "half-way-demo" for our businness managers and we're experiencing BIG INSTALLATION PROBLEMS!!! Also, I'd appreciate that you break (funny) 2GB mit for Access database... 100GB should be OK in this modern era... an especially for this project! Thank you very much in advance.

As to 3), pls, go to my post at blogs.msdn.com/.../a-chance-to-influence-the-direction-of-access.aspx.

1, we develop - install CMMS (Computer Maintenance Management Systems) to the manufacturing industry. 2, Website, Brochure and word of mouth. 3, A much more robust version of .mde to assists with copy protection. I.e. not only stopping tables being viewed in design but also queries, reports etc. A Conversion wizard. MS Access to .NET visual studio would be like gold for us.

What is the application scenario and why people use your application(s)? My app provides a workspace to operate a custom manufacturing facility (specifically joinery, but not limited to). 10 years in live development for my own business. (www.isminteriors.com.au) Running A2003 .mde in runtime environment. workgroup security active. How do customers/clients find your application(s) to purchase? The product is in early stages of marketing for sale. It is expected that specialist sales, installation and support will be required. Expect to ship with A2007 runtime once Office 2007 SP1 is released to fix shortcut menu bug with 2003 .mde. workgroup security is critical to the app design. database will not upgrade to 2007 format What features could we add to Access that would help you be more successful? A. ability to make minor formating changes to customers reports in .mde format would help in customers feel different to others using the program. (distributing .mdb is out of the question) B. I am disapointed workgroup security has been discontinued. can't it just be left alone as part of the new format ? C. My application is too complex (Cannot open any more databases problem) for a split db. We have developed a custom method for importing client data into new .mde. eliminating the need for split database. updating the file is simple, just perform an import of data to a new .mde . Generally I have not seen this option anywhere else. Is it possible can be built in as a standard option ? D. We have developed security (specifically licencing) by issueing a licence key tied to relevant information within the clients database (including renew date). It is IMPOSSIBLE to run the application without the correct key. Workgroup security was never going to cut it here. Maybe you could offer a similar method of securing db as standard E. Some how you need to build in the option to disable the importing of tables and queries (from salable db) into another db. This is a major problem in protecting IP F. Access as a platform is criticised by competitors (and doubt is planted in customers minds, not all customers are well informed). Example XYZ product uses (ANY SQL Backend). Its really great because you can have thousands of users. Fact is none of their clients will use the product in an environment with more than 10 users and for each user you must pay for a new licence. Access (shared .mde) can handle 10 users with no licencing issues. I think you need to promote the use of access as a serious small workgroup application environment. Hope this helps Contact information (via the email option). peter@icondst.com.au