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.
Bookmarks