<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 61: VSS Integration requires synch force</title><link href="https://sourceforge.net/p/querycommander/feature-requests/61/" rel="alternate"/><link href="https://sourceforge.net/p/querycommander/feature-requests/61/feed.atom" rel="self"/><id>https://sourceforge.net/p/querycommander/feature-requests/61/</id><updated>2005-11-17T10:09:22Z</updated><subtitle>Recent changes to 61: VSS Integration requires synch force</subtitle><entry><title>VSS Integration requires synch force</title><link href="https://sourceforge.net/p/querycommander/feature-requests/61/" rel="alternate"/><published>2005-11-17T10:09:22Z</published><updated>2005-11-17T10:09:22Z</updated><author><name>m.hilpert</name><uri>https://sourceforge.net/u/mhilpert/</uri></author><id>https://sourceforge.net444c62e9d7872afc846ab2d5eefa4b6f2a01a004</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The VSS Integration is almost useless as a user can &lt;br /&gt;
change objects in the database and separately in VSS &lt;br /&gt;
and he is not forced to make the change in &lt;br /&gt;
VSS/SQLServer to SQLServer/VSS. When using &lt;br /&gt;
QueryCommander, a change in the database or VSS should &lt;br /&gt;
always be marked to be synchronized. Otherwise &lt;br /&gt;
inconsistency between VSS and SQLServer is preassigned.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>