Draw a line under the product. Create 2 products:
Express/User version which ONLY has macros. (no VB projects)
The express version can be further tweaked to prevent creation of multi user projects

Professional/Enterprise Developer version for Developers

with the some stripped out features put back

The Pro version features:

1.The this version should also allow simple targeting of Mobile devices.
2.Source control
3.AZURE SQL and SQL Server projects

This will Sell MORE cloud services

4.Improve the crappy forms projects so they are as good as VS.NET (Express....)

5.Improve reports and integrate with SQL Server reporting.
Create PDF reporting

6.Scrap the new macro editor it is really annoying.

7.Present a consistant data model. Lets face it : random use of DAO, RDO, and ADO is poor practice
Follow my idea above and give us the .net data model. SCRAP DAO Support

8.Add proper stored procedures both locally and in SQLServer/Azure projects.
9.Provide an in BUILT way for backing up each section of the Accdb to source control if you persist with the single file model

10.Provide a simple way of exporting the schema as DDL
11.Provide a Cloud solution in office 365 for DEVELOPERS.
12.Remove VBA and add VB.net or C# for developers. With a developer framework library

13.DROP the single file model
14. Provide a managed back end for workgroup development in the peer currently
occupied by sqlserver express.

14.Hire me as your product manager currently this product is losing your most important customers FAST.

Well looking at that list makes me think: Visual studio: New project Type ....

Equdos is a microsoft partner.
Equdos ART Team specializes in migrating VBA projects to the cloud
and mobile devices (thanks for the work)

We have developed in EVERY version of this product.

I found a bug in the Application.PlainText() method. This method "Strips the rich text formatting from a string and returns an unformatted text string."

I don't know where else to report a bug like this. I reported the CTRL+A SQL editor bug to UserVoice and it was fixed.

I am writing a SQL formatter that will adjust the layout and colorize a SQL statement in a Rich Text box. I expect PlainText() to remove Rich Text formatting without corrupting the SQL statement.

You can reproduce this bug in the Immediate Window.

? PlainText("SELECT Record_ID,<BR>'Hello ' & Name")

correctly returns:

SELECT Record_ID,
'Hello ' & Name

but if the<BR> is before a comma, it removes the space before the "&"

? PlainText("SELECT Record_ID<BR>, 'Hello ' & Name")

returns:

SELECT Record_ID
, 'Hello '& Name

Notice that the space before the "&" is now missing.

A work-around I am testing:
replace( {text} ,"<BR>,","<BR>, ") ' (two spaces are after the comma)

1. Fix all the tiny dialogs to at a minimum be sizable.


2. Modify the linked tables manager to sort by data source. Since you can only relink one datasource at a time it makes absolutely no sense to sort alphabetically, especially when the window is so small that you can't even read half the table names, either do this easily by sorting by data source or even better by creating a source drop down and using that to filter so the form only shows tables from a particular source. I have a sample I created for my own use if you need some interface ideas, drop me a line.


3. Organize the Access options in back stage to make it CLEAR which options apply to Access itself, which to all databases opened by this version of Access, and which to the specific database.


4. Add options to help developers define properties. You keep vacillating between defaulting the Allow ZLS option from no to yes and back again. I ALWAYS want it to be NO. Please stop making me stop and think about what the Access version I am working with is set to. Another problem is your choice to default numeric values to 0. I understand it is somewhat less confusing to novices but I understand the difference between 0 and nothing and to me it has meaning so I want to ALWAYS set the default to null and then override as necessary rather than the other way around. This is of course especially problematic for foreign keys.


5. Make a better dialog for creating import/export specs. The "new" version doesn't cut it because it hides the internals so I NEVER use it and I always end up reverting to the old version when helping users who find that what seemed to be easy is so inflexible that it is unworkable. In particular, I want to be able to change a field width and have the subsequent starting locations automatically updated. Same if I remove a column.