Excel 2011

[Domski]

Get some old tech, wrap it up in a nice shiny box and charge double what anyone else does...that's the Apple way

 

[Lewiy]

Get some old tech, wrap it up in a nice shiny box and charge double what anyone else does...that's the Apple way

The one thing that really gets me is the video calling......I had phones over 5 years ago that did video calling (and over 3G too). No one ever used the functionality so everyone started removing the front facing cameras from their phones and no-one complained. Then Apple come along with this fantasic new idea "you can call people and see them at the same time with a front facing camera, oh, but you can only do it over wifi, when you're probably stood next to your Mac anyway".

And people go "oooh I must get me one of those!"

 

[Domski]

Exactly!!! I know the phone I had six odd years ago had 3G and video calling and I didn't use it then and am pretty sure I wouldn't now.

Let's face it the last thing you want is the boss seeing you when you ring in sick

As the Daily Mash puts it..."Shiny thing make it all better".

Dom

 

[Greg Truby]

I thank Steve Jobs for the Mac on a routine basis. My mother and my brother-in-law, Ted, both went with Macs. So whenever my mom has any kind of a tech issue... "you know, Mom, I really don't know anything about Macs. You probably need to call Ted on that one."

 

[PaddyD]

On the subject of apple-fetishisation, I'm sure people have seen this, but in case they haven't:

http://www.youtube.com/watch?v=FL7yD-0pqZg

(nsfw)

 

[PaddyD]

"My mother and my brother-in-law, Ted..."

It must be confusing, having both of them called Ted.

 

[bauerjang]

Hello MrExcel-Forum,
I have a few questions about running macros with VBACode on Mac:

in another thread I could find a few rules to respect:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
1) Avoid use of reverse-slash as a path separator. Instead, use Application.PathSeparator
2) Don't use chr(10) or chr(13) or whatever constitutes a 'new line' on a specific platform.
Use vbNewLine. Similarly, use other available VBA mnemonics such as vbNull.
This transfers to the computer the responsibility of correct hex codes.
3) Minimize the amount of 'hard coding' of anything.
For example, use LBound(array) and UBound(array) to get array limits
4) Many recommend the use of 65536 as a hard-coded value for the number of rows.
The most frequent example is (partially correct) code to find the last used cell in a column as in Cells(65536,1).End(xlUp).
The more flexible (and still only partially correct) alternative is Cells(Rows.Count,1).End(xlUp).
5) Use Application.OperatingSystem to figure out what OS the code is executing under.
Also, use the Environ function to further interrogate the OS configuration.
>>>>>>>>>>>>>>>>>>>>
But a few more questions , I'm a littele confused:
-Are there restrictions on using the CommonDialog in Userforms?
-How working with .path or .folder ? (documents stored in Mac)
-Are any changes in actions like : Activewindow.close or application.quit
or : ActiveWorkbook.Close False ?
or in displaying like : Application.DisplayAlerts = True

I have no Mac to test my macros issued from a WinPC with Excel2003,
so before sharing my ExcelApplications, I would like to the known restrictions.

It is my first post, hope I'm not to wrong here
Greetings & THX for your reply

 

[SydneyGeek]

It's been a while since I wrote anything for Mac (back when Windows used Office 97 and Mac had Office 5) BUT most of the object model seemed to work interchangeably. The problem came when you make calls to the system (API) because they were very different.
Others can comment further but I think that is still the case...

Denis

 

[mikerickson]

Hello MrExcel-Forum,
I have a few questions about running macros with VBACode on Mac:

in another thread I could find a few rules to respect:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
1) Avoid use of reverse-slash as a path separator. Instead, use Application.PathSeparator
2) Don't use chr(10) or chr(13) or whatever constitutes a 'new line' on a specific platform.
Use vbNewLine. Similarly, use other available VBA mnemonics such as vbNull.
This transfers to the computer the responsibility of correct hex codes.

Good practice on any platform, the speed of getting a constant (eg. vbCR) is faster than calculating the function Chr(133)

3) Minimize the amount of 'hard coding' of anything.
For example, use LBound(array) and UBound(array) to get array limits

Similarly, good practice on any platform. Lower bounds are not affected by platform.

4) Many recommend the use of 65536 as a hard-coded value for the number of rows.
The most frequent example is (partially correct) code to find the last used cell in a column as in Cells(65536,1).End(xlUp).
The more flexible (and still only partially correct) alternative is Cells(Rows.Count,1).End(xlUp).

Another good, not Mac specific practice.

5) Use Application.OperatingSystem to figure out what OS the codeis executing under.
Also, use the Environ function to further interrogate the OS configuration.

look into conditional formatting

#If Mac Then
    Rem code for Mac
#Else
    Rem code for Windows
#End If

>>>>>>>>>>>>>>>>>>>>
But a few more questions , I'm a littele confused:
-Are there restrictions on using the CommonDialog in Userforms?

What are CommonDialogs? The use of built-in dialogs (even InputBox) while running a userform is not wise

-How working with .path or .folder ? (documents stored in Mac)

Application.GetOpenFilename works on a Mac, to get a folder use MacScript("choose folder")

-Are any changes in actions like : Activewindow.close or application.quit
or : ActiveWorkbook.Close False ?
or in displaying like : Application.DisplayAlerts = True

Those work as on Windows.

 

[arkusM]

I was hoping for an eye witness report that MS marketing had not been optimistic.

I just fired up a copy on the weekend and it *appears* to have VBA in there but I have not tried to code anything yet or bring some work apps home to try.