Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Moving from PC to Apple

Status
Not open for further replies.

mtd081011

Technical User
Aug 16, 2011
11
US
I will be moving from an old PC to an Apple. I work with Excel a lot and I know there are some differences between PC's and Apple's when working in Excel. Besides this forum, is there a good source I could use to help me navigate Excel using an Apple? Thansk.
 
When I attempted to convert some VBA-driven spreadsheets from Excel-2010 (Windows) to Excel 2011 (Mac) a large amount of the VBA ceased to run. I might eventually have been able to get it working, but since I was merely attempting a favour for a friend I gave up.

I never got a chance to see how the Excel environment (as opposed to the VBA environment) converted.
 
Deniall,

I'm curious on what you mentioned. Did the VBA have a lot of calls outside of Excel? So, did it call up Windows objects? I remember reading that there are many objects that work on Windows but do not on Mac. It makes sense for the Windows-specific objects, but I wasn't sure whether that was also the case for Excel or Office-specific objects.

"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57
 
My troublesome spreadsheet used no "calls outside of Excel". It used mainly Command Buttons to run slabs of VBA code, slabs that were quite large but not particularly demanding in terms of features. It also used quite a bit of event-driven code.
 
Have you discovered Ron de Bruin's web page on Macintosh Excel & VBA?

Mac VBA doesn't accept ActiveX controls. You must use Forms controls instead.

The path separator is different, so code that concatenated a file path will need to be revisited. You might consider using Application.PathSeparator instead of hard-coding \ or :

 
Thanks for the heads-up. I do have a dashboard of hyperlinks I use to navigate which I know will not work as soon as I go to a Mac. I am sure I will be able to work through this. Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top