There's two basic questions that we need to answer when talking about porting an app. This is true for any app that we could port, not just Access. 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. What is the business need for the application? How many users want it, and how much are they willing to pay for it? 'Expense of porting' isn't really about money, but is rather about time and the experience of the team that would develop it.
To this day, Microsoft Office programs for Mac include mainstays like Microsoft Word, Microsoft Excel, Microsoft Outlook, Microsoft Access, and Microsoft Publisher. By owning the full MS Office Suite, it is easy to transfer important information across each different program for better presentation and deliverability. The latest version of Microsoft Office 2011 for Mac does not contain the Access program. None of the Microsoft Office versions for Mac contain Access. So the only way to use Access on a Mac is to use some sort of a program that allows Windows programs to run on a Mac.
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. 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. 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. 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. If this is important to you, you should to us about it. 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 you work for a large company, you should instead route this feedback to your Microsoft account rep. Regards, Nadyne. Click to expand.As Cromulent already pointed out, Excel, Word, and PowerPoint were all on MacOS X long before Apple introduced the iWork suite. But it goes even further than that: Excel came out for the Mac 2 years before it was ported to Windows (which in pre 3.0 versions was fairly unused when Word and Excel came out), and Microsoft Word was one of the first programs for sale for the Macintosh in 1984.
The real reasons are probably a mixture of the difficulty of porting the legacy codebase that is Access, the desire to make sure that some businesses feel locked-in to the Windows platform (since they have custom code written in Access supporting critical parts of their business), and the perceived difficulty of breaking into the Mac database market (because of the strength of FileMaker and others like 4D). To better explain my situation. I go to Bryant University in RI and we are given Lenovos T61 at the beginning of our Freshman and Junior years (I sold mine this year and bought a unibody Macbook). I've been trying to convince the IT department to open the program up to a choice (students could choose Macbook or Lenovo). Its an uphill battle to say the least.
In our CIS classes (everyone's required to take one) we use Access. As a result, I was hoping that a mac version would be released so I could use it in any classes I need it or in future business or careers. I have an internship coming up this summer that I may or may not be using Access. It would be nice not to ruin my unibody by putting Windows on it, but its looking more and more like that will have to happen.
Also, I need to use Excel pretty elaborately next semester and I'm pretty sure Excel for Mac (which I got the free trial yesterday for) will not suffice. Can anyone give any insight on this? Click to expand.A quick little history for you. Excel was created for the Mac platform first. Then around version 3.1 it was ported over to Windows. In 1997, Microsoft released Office 97 for the PC, then in 1998, Microsoft released Office 98 for the Mac.
These were my favorite versions when it came to the menu system. They were identical on both platforms. To this day, I don't see why Microsoft doesn't develop identical office suites for Mac, Windows and Unix/Linux platforms all available on one install DVD. This way you purchase one copy and you can install it on your platform of choice. Also make it multi-lingual and support Unicode across the board. Everything should be identical on all three platforms.
This means 100% compatible with the same menus, features, etc. One, this would make Office a much better standardized suite. And two, it would spur sales because individuals could purchase one version that would work on whatever they have at home which would complement their work Office suite. Microsoft wins either way.
As it is now, the MBU looses sales everyday due to compatibility, lack of VBA and other issues not to mention there is no Access equivalent. Unfortunately, it seems that Microsoft does not seem to think in these terms. What's really interesting is back in 1986 there was a company called Aston-Tate that released dBase Mac for the Mac OS. It was awesome. In fact, it wasn't until 2002, that Access caught up with with dBase Mac when it came to creating relationships graphically by dragging your mouse. Click to expand.Thanks for your post Nadyne. My suggestion is above.
With the talent at Microsoft, I would venture to say that this could be done within a few years if Microsoft wanted to do it. Mac sales are growing. Most I know who run office and need 100% compatibility with the Windows version run Office 2007 on the Mac via virtualization via VMware or Parallels. Just think how many more sales the MBU would have if these same individuals could purchase Office for the Mac that would be the same. Here's hoping to the day that Microsoft releases Office 20xx that contains Word, Excel, PowerPoint, Access and Outlook for all three platforms (Windows, Mac and Linux) on one nice install DVD. Now that would be suite, er.
To better explain my situation. I go to Bryant University in RI and we are given Lenovos T61 at the beginning of our Freshman and Junior years (I sold mine this year and bought a unibody Macbook).
I've been trying to convince the IT department to open the program up to a choice (students could choose Macbook or Lenovo). Its an uphill battle to say the least. In our CIS classes (everyone's required to take one) we use Access. As a result, I was hoping that a mac version would be released so I could use it in any classes I need it or in future business or careers. I have an internship coming up this summer that I may or may not be using Access. It would be nice not to ruin my unibody by putting Windows on it, but its looking more and more like that will have to happen. Also, I need to use Excel pretty elaborately next semester and I'm pretty sure Excel for Mac (which I got the free trial yesterday for) will not suffice.
Can anyone give any insight on this? Click to expand.I seem to recall having this conversation with you in the past. Mac users have very different expectations than Windows users. I know that you liked Office 98, but I'm pretty convinced that you're the only person in the whole world. I've long since lost count of the number of Mac users who have come up to me and told me that they absolutely hated Office 98 and never ever want us to walk down that path again. To compare it to the number of people who've told me that they wish we'd do another Office 98. Well, I'm up to one request, so far.
There's plenty of places where it just doesn't make sense for us to simply follow Office for Windows. For example, we want to plug into the right technologies for our Mac users: all the Core technologies, Spotlight, AppleScript, Automator. The list is extensive.
Likewise, we want to support other apps on the platform that our users rely on, such as iPhoto. Now, that said, if you can prove to us that the sales that you posit we'd gain from being 100% identical to Windows Office would be greater than the number of sales that we'd lose for not being a good Mac application, then you might want to put together a pitch deck and send it to our marketing team to see if you can get a gig with us and make your vision happen. Regards, Nadyne. There's plenty of places where it just doesn't make sense for us to simply follow Office for Windows. For example, we want to plug into the right technologies for our Mac users: all the Core technologies, Spotlight, AppleScript, Automator. The list is extensive.
Likewise, we want to support other apps on the platform that our users rely on, such as iPhoto. Now, that said, if you can prove to us that the sales that you posit we'd gain from being 100% identical to Windows Office would be greater than the number of sales that we'd lose for not being a good Mac application, then you might want to put together a pitch deck and send it to our marketing team to see if you can get a gig with us and make your vision happen. Click to expand.This is why I worry about Microsoft management. With Office you can customize the heck out of it.
What is so hard about having a simple toggle button for example, that allows the Mac version to have an interface like the PC version or be Mac like? What I can tell you, is that when I work with switchers, this is how it goes: Switcher: Will my copy of Microsoft Office 2003/7 work on the Mac. There is a really cool version of Office for the Mac. I demonstrate Office for the Mac. Switcher: So it is 100% compatible? Me: Well, yes, mostly.
Switcher: So there is VBA support? Switcher: Is there Access? Switcher: How about Outlook? Not OE but real Outlook? Switcher: I notice the interface is different.
Why is the Mac version different? Well to take advantage of the Mac's GUI and feature set. Switcher: But it's not like the PC version. So that means I will have to lern a new interface. It's not all that different and you can do the same things. Switcher: Except VBA and Access, right.
Me: Well true. The end result is this. I usually recommend getting VMware/Parallels, run XP and Office 2003 or 2007. Nadyne, I know that you mean well so I will offer you this. I work with military and government types.
At work they have PCs. When taking work home, they don't want to spend the time learning a different interface from work. It's simply not worth it to them. The same holds true for those I know who work in Fortune 500 companies.
There is a huge sales potential being completely missed by Microsoft because the Mac and PC versions are not the same. Just think of all the individuals out there in government, military and Fortune 500 types that would love to use the Mac version of Office at home decide it is better and much easier to use the Windows version because it's obviously 100% compatible, has Access and Outlook. Anyhow, I hope someday that Microsoft will consider releasing cross platform, 100% compatible, office suite that includes Excel, Word, PowerPoint, Access and Outlook.
I know that I am probably dreaming, but what the heck? Click to expand.Okay, this brings up a good question. What is a Mac user?
I can think of these types of Mac users from top of my head:. Always have used Macs from day one. Expect everything to be Mac like. Always have used Macs from day one, but work in a PC centric environment. These users usually have Macs at home and use PCs at work. Individuals who have changed from the PC to the Mac.
From my experience, many would like to use Mac only software, but in the case of Office are forced to use the PC version because they need VBA, Access and Outlook. They also get frustrated at the Office suite interface differences. Have used both platforms from day one (DOS 1.0 and the first Mac). These folks generally use both and like the different features of both, but like common interfaces as it makes it easier to use.
Office allows for customization of menu bars and such. Why not simply have a toggle that allows Mac like interface for those who want it and an identical PC interface for those who have to use each on a daily basis. While it would take a bit to implement this, it is not rocket science. Click to expand.Clearly, you have never built a rocket, not have you ever developed a computer application.
There are applications that sort of do what you suggest. They have selectable themes, Firefox would be an obvious example. If you had ever closely examined the widgets in different themes in an application that supports this feature, then you would known that not all themes are equal. Some appear to be native. Others are shoehorned and/or stretched to fit. Beneath the most obvious level, you have something that really is neither fish nor foul. Firefox may have many virtues, but behaving like a true Mac or Windows application are not among them.
What you are talking about is probably an order of magnitude more complex that Firefox themes. There are applications that sort of do what you suggest. They have selectable themes, Firefox would be an obvious example. If you had ever closely examined the widgets in different themes in an application that supports this feature, then you would known that not all themes are equal.
Some appear to be native. Others are shoehorned and/or stretched to fit. Beneath the most obvious level, you have something that really is neither fish nor foul. Firefox may have many virtues, but behaving like a true Mac or Windows application are not among them. Rocket science is an informal term for aerospace engineering concerning rockets which launch spacecraft into or operate in outer space. Due to the complexity and depth of this area of engineering (requiring mastery in subjects including mechanics (fluid mechanics, structural mechanics, orbital mechanics, flight dynamics), physics, mathematics, control engineering, materials science, aeroelasticity, avionics, reliability engineering, noise control, flight test), it is also informally used, much like brain surgery, as a term to describe an endeavor requiring great intelligence or technical ability. Often the term is used ironically to describe an endeavor that is simple and straightforward by stating 'it's not rocket science' (one of the top ten irritating phrases, according to research at Oxford)1 or 'it doesn't take a rocket scientist'.
It is also used ironically to describe a person who is simple-minded: 'He/she's not a rocket scientist.' Click to expand.I would venture to say that Rocket science is a bit tougher than developing software applications. But that's just me. Anyhow, we are getting a bit off topic here.
The original question was in the thread title. I believe that it has been answered. To finish, who knows what Microsoft has up it's sleeve or will be developing.
Personally, I am a fan of Office for the Mac and PC. I use it for work and personal tasks. Maybe that is why I am so passionate to see a identical cross platform suite with the same menus and interface, but yet, at the same time have the option for Mac specific.
Image: Apple the most seasoned Mac users sometimes need to access Windows applications to get their work done. While the two ecosystems were at odds with each other for most of their early days in the enterprise, there are now many options for Mac users who need to access a Windows app or server. Tools like Parallels and Virtualbox are popular among users but, for years, one of the standard applications for connecting the two systems is the Microsoft Remote Desktop connection. And, fortunately, the process for downloading and using the Microsoft Remote Desktop on macOS Sierra is fairly straightforward. Note: If you want to access Microsoft Remote Desktop on an older version of Mac OS X, check out.
As with most modern Mac applications, Microsoft Remote Desktop is available for download through the Mac App Store. Go to the icon Dock on your desktop and click the blue 'App Store' icon to open it. Inside the Mac App Store, type 'Microsoft Remote Desktop' into the search bar at the top right hand portion of the window.
The option you want is an orange icon with a computer monitor on it. It should be the first option listed. To begin downloading Microsoft Remote Desktop, click the blue 'Get' button.
This app is free, so no price will be listed.Once you click on 'Get,' the button will turn green and say 'Install app.' Click the button again. For here, you can close out the App Store. To access the newly downloaded app, click the the grey 'Launchpad' icon in the Dock. Click the Microsoft Remote Desktop app icon to open the app.
If you can't seem to find the icon (it will look the same as it did in the App Store), try swiping left. If you have many application, the Launchpad will have multiple pages. Another way to find the app is by using the Spotlight Search feature, which you can access by clicking the looking glass at the top right of your home screen, or by using the shortcut Command + Spacebar. Once you have Spotlight open, type 'Microsoft Remote Desktop' and hit enter. Once open, the app should look like this: When you first open the application, you may be presented with a pop up window alerting you to what is new in Microsoft Remote Desktop. Feel free to close that window and continue on.
If you want to be able to quickly return to this application in the future, you should set it in your dock. To do so, right click (control + click) on the icon, mouse over 'Options,' and click 'Keep in Dock.' This will keep you from having to look for the icon every time you need to use it. At this point you'll need to enable remote access on your target PC. For a Windows 10 machine, head to the start button on the bottom left of your desktop. Click the start button and then click 'File Explorer.'
In the next window, on the left side of the screen, right-click the option that says 'This PC' and then click 'Properties' at the bottom of the following pop up window. In the system properties window, click on 'Remote settings' on the left-hand side. Make sure the radio button next to 'Allow remote connections to this computer' is clicked.
Also make sure the box next to 'Allow connections only from computers running Remote Desktop with Network Level Authentication' is checked if you have that authentication. If you want to get to this part faster, simply type 'Remote Settings' in Cortana from your Windows desktop and and click the search result that says 'Allow remote access to your computer.' You'll also need your full PC name if you don't already have it, which will be used to set up the connection. Click on the start button and then click 'Settings' and the 'System.' At the bottom of the next window click 'About' and the PC name should be available at the top.
Enabling a Windows 7, Windows 8, or Vista machine is a little different, but you can find out how to do that. Once you have enabled remote access and have the PC name, go to your Mac and click the 'New' button at the top left of the Microsoft Remote Desktop screen. You'll be prompted to fill in a few fields. First, you'll input the connection name. This is just an arbitrary name and has no real bearing on the connection itself. For example, you could call it 'Sarah's work PC.'
Next, you'll need to input the PC name (the one you wrote down from earlier), or the IP address so your Mac knows where to find the PC. The next line down allows you to configure a Gateway, which would allow a connection to virtual desktops or session-based desktops available on your company's network. Be sure to check with your network administrator to see if there is a gateway you are supposed to use. Credentials is where you will type in the domain, username, and password for the target PC so you can log in through the remote connection.
Once again, check with your IT admin, but these should be your standard username and password for your target machine. Resolution, colors, and full screen mode are all personal preferences for how you want the remote desktop to launch on your machine. If you're not sure, start with the standard settings and go from there. In the same window, click the 'Session' tab in the middle to configure peripheral devices for your remote desktop.
With the 'Sound' drop-down, for example, you can choose where you want any sound to play. Clicking the box next to 'Connect to admin session' will allow you to connect to an administrator session on a Windows server, and 'Forward printing devices' will make your local printers available during your remote desktop session. 'Swap mouse buttons' will allow you to use left click commands with a right-click Mac mouse. The third tap at the top of this window is 'Redirection.' Here, you can choose a local folder to be made available during your remote session.
Click the '+' button, choose a name for the folder, and input the folder's path to have it available. When you are finished configuring your remote desktop, click the red close button at the top left of the dialog box and your new remote desktop will be added. To start a session with that desktop, simply double-click it to begin. If you want to edit, duplicate, export, or delete that remote connection, right-click (control + click) on the desktop name to access those options. What do you think? Is there a better way to access your Windows applications? Tell us in the comments.