These were my favorite versions when it came to the menu system. In 1997, Microsoft released Office 97 for the PC, then in 1998, Microsoft released Office 98 for the Mac. Then around version 3.1 it was ported over to Windows. If you work for a large company, you should instead route this feedback to your Microsoft account rep.Ĭlick to expand.A quick little history for you.Įxcel was created for the Mac platform first. Tell us why you want Access on your Mac, how it impacts you to not have it, and what you're doing because you don't have it. If this is important to you, you should submit a suggestion to us about it. We revisit our application portfolio frequently to make sure that we're still doing the right thing, so maybe that will change in the future. In the particular case of Access, the cost of porting the application is high, and the business need hasn't yet been high enough for us to incur the cost of porting the application. It's a place where we'd need highly-experienced Mac developers, and they'd need a fair amount of time to make it happen. When you're talking about an app as complex as Access, we couldn't just hire a bunch of fresh college grads and throw them at it. "Expense of porting" isn't really about money, but is rather about time and the experience of the team that would develop it. What is the business need for the application? How many users want it, and how much are they willing to pay for it? What is the expense of porting the application? If the application is built using a lot of Windows-specific code and APIs, then the expense of porting the application is much higher than if not.Ģ. This is true for any app that we could port, not just Access.ġ. There's two basic questions that we need to answer when talking about porting an app.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |