• Status: Solved
  • Priority: High
  • Security: Public
  • Views: 37
  • Last Modified:

Failed to export report to a file - Source Safe and Access

I have had an environment of Access 2002 (yes, I know - no comments needed here - we are working on migrating) for which we use Source Safe (v6) to control object changes in a multi-developer environment.  

Last week, all of a sudden, when I try to check in an object I keep getting error messages - leading me to believe that perhaps my Source safe installation is corrupted.  However, today I reinstalled Source safe and to no avail, got the error again.  

The one I'm dealing with right now is "Failed to export report 'rpt......' to a file.".  I've tried deleting the project and pulling it down fresh and reinstalling VSS.  It's weird because it lets me pull down the project without any errors and even check out objects without error.  However, as soon as I try to check my object back in - it gives me this, or a similar, error.  The only recovery is to delete the object and import it from a previous build (mdb outside of VSS).  Then I have to delete my project, bring it down fresh and sometimes I can get one change in before it happens all over again.  HELP!
0
SpaceCoastLife
Asked:
SpaceCoastLife
  • 2
  • 2
1 Solution
 
PatHartmanCommented:
I don't know much about Source Safe but this sounds like you might have run out of space in the database that SourceSafe is using.  I would look into how that space is defined.  Perhaps it needs to be reorganized and expanded.
0
 
SpaceCoastLifeAuthor Commented:
The only way I've been able to get around this is to start Access as 'Run as Administrator' - then open my project.  However, before last week I didn't have to do this.  I can only suppose that one of the Microsoft updates caused this issue - but I don't know which one.  It's not ideal, but it works!
0
 
SpaceCoastLifeAuthor Commented:
This is the only solution that I found that worked after trying to analyze and repair the SS database, reinstall Access, reinstall sourcesafe.
0
 
PatHartmanCommented:
Thanks for telling us how you resolved the issue.  It does sound like some security change.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now