New Access / SourceSafe Bug Discovered

So, we recently spent the last few hours chasing a rather obscure
bug... We thought we would share with the group in the hopes that
someone else finds this information useful.

We use Access 2003 with SourceSafe for our current projects. We
recently has a problem where Access would crash when we would "Get
Latest Version" of a certain report.

After an exhaustive search, we found the culprit. We had used high
ASCII in one of the labels (specifically, it was a right arrow
character).

It appears that since SourceSafe imports and exports to text, that the
SourceSafe parser was unable to deal with high ASCII characters in a
label.

To resolve the problem, just do not use high ASCII in your labels
(likely other controls too), if you plan to use SourceSafe.

Hope this helps.

-Ben

.

Relevant Pages

  • Re: New Access / SourceSafe Bug Discovered
    ... >We use Access 2003 with SourceSafe for our current projects. ... just do not use high ASCII in your labels ...
    (comp.databases.ms-access)
  • Newbie needs label scripts/script info
    ... have scripts to apply labels on not just a project but onto individual ... The following list outlines the scripts required: ... I'm relatively new to SourceSafe, and the time I've had to do any ramp ... up to learn more about SourceSafe beyond source control has been very ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: Newbie needs label scripts/script info
    ... down the wrong path using file labels. ... > The following list outlines the scripts required: ... > - label folder and files recursively ... > I'm relatively new to SourceSafe, and the time I've had to do any ramp ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: Tool for SQL Server source code management
    ... It links into SourceSafe so you can extract the source from labels or build a database using the latest code and it can deploy the net code changes including my static data. ...
    (microsoft.public.sqlserver.tools)