Office 2003 SP3 breaks MS-Access Sourcesafe

[Guest]

Since installing Office 2003 SP3 I've been unable to get the forms etc in my
MS-Access projects from SourceSafe.

When it gets to importing the forms I get these error messages:

Microsoft Office Access
(x) There isn't enough memory to perform this operation. Close unneeded
programs and try the operation again.
[OK]

Source Code Control
(i) Failed to import file
'c:\fvs_uk_apps\arm_axa_bpp.scc\FrmEndorsement_Policy.ACF' into Microsoft
Access.
[OK] [OK All] [Help]

The first error seems misleading, 3gb RAM/17gb free disk and the error
happens consistently whatever programs are loaded.

The help for the second message says "Check that the object is not corrupted
and that the object is consistent with the version in the Visual SourceSafe
project." The head of the .acf file has
Version =20
VersionRequired =20
When I create a new database with a blank form in the patched MS-Access and
add that to Sourcsafe it has
Version =19
VersionRequired =19
This new project can be imported without any problems.

I had a similar problem before when the setting in
"Tools|Options|Advanced|Default File Format" was set to Access 2000. I've
checked that this is set to Access 2002 - 2003. When it is set to Access 2000
and try to import the memory error doesn't appear but the second one still
does and the forms etc are not imported.

I also have Access XP installed on my machine. That is still working fine as
long as the Default file Format option mentioned above is set to the later
version. I can open the file created with XP in 2003 but when I try to check
out/in a form I get the same error messages.

I think the service pack has broken the SaveAsText/LoadFromText functions
that Sourcsafe uses. They are no longer using the correct verision number in
the header. I'd welcome any other ideas, or a fix/workaround for it. At the
moment I'm using MSAccess-XP instead.

 

[Paul Shapiro]

I got some form and report corruption with the same error message when I
installed Office 2003 SP3. The problem occurred in about 10% of the objects,
not all of them. In my case I was able to resolve it by deleting the problem
objects and importing them from an older version of the mdb, a copy that had
never been opened in SP3. MS tech support also found that the corruption
could be removed by exporting the corrupt objects with
Application.SaveAsText and then importing the object from the text file with
Application.LoadFromText. In my case, once the objects were "clean" the
corruption does not seem to recur.

I got the working versions into SourceSafe by first deleting the corrupted
objects from SourceSafe, working in the SourceSafe user interface, and
purging the project to remove those objects completely. Then I imported the
working objects into the SourceSafe-controlled mdb one at a time. After
importing each one, I opened it to make sure it was working ok. After
closing it I added it to SourceSafe.

I had similar issues using a db created from SourceSafe with Access 2003 SP2
and then opened in Access 2007. In that case the fix was making sure the
objects had all been opened once in Access 2003 before trying to open them
in Access 2007. Or for some of those problematic forms, removing the hotkey
settings from one or two controls made the forms work without problems. I
think SP3 introduced some similar changes from Access 2007 into Access 2003.
Paul Shapiro

Since installing Office 2003 SP3 I've been unable to get the forms etc in
my
MS-Access projects from SourceSafe.

When it gets to importing the forms I get these error messages:

Microsoft Office Access
(x) There isn't enough memory to perform this operation. Close unneeded
programs and try the operation again.
[OK]

Source Code Control
(i) Failed to import file
'c:\fvs_uk_apps\arm_axa_bpp.scc\FrmEndorsement_Policy.ACF' into Microsoft
Access.
[OK] [OK All] [Help]

The first error seems misleading, 3gb RAM/17gb free disk and the error
happens consistently whatever programs are loaded.

The help for the second message says "Check that the object is not
corrupted
and that the object is consistent with the version in the Visual
SourceSafe
project." The head of the .acf file has
Version =20
VersionRequired =20
When I create a new database with a blank form in the patched MS-Access
and
add that to Sourcsafe it has
Version =19
VersionRequired =19
This new project can be imported without any problems.

I had a similar problem before when the setting in
"Tools|Options|Advanced|Default File Format" was set to Access 2000. I've
checked that this is set to Access 2002 - 2003. When it is set to Access
2000
and try to import the memory error doesn't appear but the second one still
does and the forms etc are not imported.

I also have Access XP installed on my machine. That is still working fine
as
long as the Default file Format option mentioned above is set to the later
version. I can open the file created with XP in 2003 but when I try to
check
out/in a form I get the same error messages.

I think the service pack has broken the SaveAsText/LoadFromText functions
that Sourcsafe uses. They are no longer using the correct verision number
in
the header. I'd welcome any other ideas, or a fix/workaround for it. At
the
moment I'm using MSAccess-XP instead.

 

[Guest]

Thanks Paul, I don't think this is the same problem, I didn't get corruption
as such and the problems happened with all the objects. I can still get to
the objects from Access XP.

 

[kelliek]

I had the same problem which was caused by too many click buttons on a
form.
It was ok in Access 2003 but not in Access 2007. So I went back to
ACC03 removed some buttons and the macros they ran, opened it in ACC07
and all was well.
For 3 weeks.
Now I get an out of memory error in both ACC03 and ACC07.
I am suspicious of updates or a new program called WebRoot which
searches for spyware.