You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
Tips
How-to
News
Videos
Stories
Luke Chung of FMS, Inc. has written an article about how to avoid performance slowdowns when adding lots of Access objects to Visual SourceSafe. Here’s an excerpt:
Using Microsoft Visual SourceSafe (VSS) with Microsoft Access for system development is great for tracking old versions, maintaining a professional Access development platform, and multi-developer environments. Being able to quickly see old versions of individual objects, differences over time, and check-in and check-out objects to prevent multiple developers from changing the same object are all wonderful features. Unfortunately, as Access databases get more objects, VSS slows down and can sometimes take minutes to add a new object to the database. Waiting for VSS to prompt you for every new object not only wastes time (especially if you don't want to add a temporary object to VSS), it disrupts the rhythm of system development. Fortunately, there's an easy way to work around this.
Using Microsoft Visual SourceSafe (VSS) with Microsoft Access for system development is great for tracking old versions, maintaining a professional Access development platform, and multi-developer environments. Being able to quickly see old versions of individual objects, differences over time, and check-in and check-out objects to prevent multiple developers from changing the same object are all wonderful features.
Unfortunately, as Access databases get more objects, VSS slows down and can sometimes take minutes to add a new object to the database. Waiting for VSS to prompt you for every new object not only wastes time (especially if you don't want to add a temporary object to VSS), it disrupts the rhythm of system development. Fortunately, there's an easy way to work around this.
Read the whole article here!
Luke Chung, President and Founder of FMS, Inc., has written and presented a wide range of topics related to Access over the years. In addition to their many Access related products, FMS offers a wealth of great Access papers, tips, and video on their site.
Comments: (3) Collapse
Good pointer, Luke! Now, is there any chance of sweet-talking Microsoft into BUNDLING VSS with Office/Access? I have an old copy of VS2003, just to keep VSS in the toolset. Seeing that Access 2010 still points to it, there must be some thinking that it's worth keeping around.
I'm more concerned about the fact that VSS is more or less deprecated (last time I looked there wasn't an explicit statement but at same time, there wasn't any update or even a little version bump - latest is 2005) and Team Foundation Server (there's a personal edition as well ) is supposed to replace VSS but when i tested, I found that the provider doesn't seem to work well. The provider also does not seem to work that well with different SCC program. For example, Access always crash if SourceGear Vault is used instead. I also wonder with SharePoint's replication functionality, is Access team going to relegate the VSS integration to legacy features that won't be developed any further?
I Like office/access can i put a cal on access?
Comments: (loading) Collapse