Portable VBA to support OSX and Windows

I have a healthy sized macro (>500k as xlam) that was written against Excel 2010 for Windows. The macro examines ActiveSheet, formats it differently depending on the type of report, and saves it to a SAMBA network share, mapped as a drive letter and accessed through the drive path (as opposed to UNC pathing). It is also responsible for reading in and writing some simple lists that are delimitated with CRLF, also stored in that SAMBA share.

Making the macro work on my OSX laptop would be helpful but is not essential, so I am trying to evaluate the considerations that need to be made for my code to be portable between platforms. Below is a list of considerations I am aware of. If you have any tips to address these concerns or know of concerns I haven't thought of, please chime in!

1) Pathing: Maybe set a PATH_DELIM global constant in my bootstrapping that tells it which way to flip the "/"?

2) Newline termination: Since Windows and OSX will both be reading/writing to the same ASCII TXT files, I think I need to pick a convention and use vbCrLf specifically rather than vbNewLine even if Split(sTextReadIn, vbNewLine) will see CRLF and split anyways. This is to maintain readability of the TXT files in Window's Notepad.

3) Anything else? Are there Windows only functions that don't appear in OSX VBA? Do any common functions behave differently between the two platforms?

Thank you.

Hi,

Re #1 application.pathseparator should be of benefit.

There are many small differences between Mac and Windows VBA and no complete listing that I am aware of. Have you not tested the code on your laptop?

As you have not posted any code, you are essentially asking for a list of all known differences and, as I mentioned earlier, there is no such thing to my knowledge.

Originally Posted by xlnitwit

As you have not posted any code, you are essentially asking for a list of all known differences and, as I mentioned earlier, there is no such thing to my knowledge.

I would have to disagree. I specifically outlined 2 issues I know I will have. Path separations and newline termination handling. I did leave the post open with #3 so that anyone with direct experience in porting VBA from Windows to OSX could chime in on any area they feel important without feeling like they are off topic for the thread. You have already solved issue #1. Thank you for your contribution.

Edit:

Earlier, I tossed some rep your way for the .PathSeparator suggestion. I have not marked this thread as solved because I intend to use it to aggregate problems that I face regarding this topic so that anyone facing this issue can use it to help understand some of the issues they may face. As you have pointed out, no such list exists.