On 6 March 2014 12:18, David Kean <[email protected]> wrote: > Thanks. It's a known issue that we're tracking and coming up with a plan to > address those VS customers affected by it.
Good. It's not too hard to find once you decide to start Googling for the problem, but, like I said in my StackOverflow question, I originally assumed it was something I did. -- Regards, Mark Hurd, B.Sc.(Ma.)(Hons.)
