ASP.NET, SQL Server, WPF, C#, VB.NET

We've just run TSI unreplicator, which eliminated 90% of the size of a back 
 
end db.  The unreplicated version ran really well. 
 
On re-replicating the db, one form cannot have its datasource updated 
 
without crashing the application.  This does not happen following 
 
unreplication, only after subsequent re-replication. 
 
Does this suggest what might be the cause? 
 
Nick

"Nick" <nickmirro@spamarrest.com> wrote in 
 
news:O3iCjX1uGHA.5084@TK2MSFTNGP04.phx.gbl: 
 
Replicating forms/reports/etc. is not viable. Split the database 
 
into back end (tables only) and front end (everything else) and 
 
replicate only the back end. That is the only way replication works 
 
in the long term. 
 
-- 
 
David W. Fenton                  http://www.dfenton.com/ 
 
usenet at dfenton dot com    http://www.dfenton.com/DFA/

David, 
 
The front end is not replicated.  Our developer has this to say regarding a 
 
possible cause: 
 
"This error does not occur to tables with fewer relationships. But here in 
 
our case the Case_details table has very complicated relationships, and has 
 
almost all tables related to it. Hence this error is occuring." 
 
May I ask your opinion of his position?  Thanks again for your kind help. 
 
Nick 
 
"David W. Fenton" <XXXusenet@dfenton.com.invalid> wrote in message 
 
news:Xns981AAF5D33110f99a49ed1d0c49c5bbb2@127.0.0.1...

"Nick" <nickmirro@spamarrest.com> wrote in 
 
news:upqC8eMvGHA.4872@TK2MSFTNGP02.phx.gbl: 
 
Perhaps the relationships are circular and cannot be resolved by Jet 
 
replication? 
 
I try to avoid circular relationships in replicated apps when they 
 
can flow in both directions. That is, if you must have a circular 
 
relationship, make sure the actual order of data entry always goes 
 
in the same direction around the circle. 
 
However, upon going back to your statement of the problem, I think 
 
the cause is something else entirely. You wrote a couple of posts 
 
back: 
 
Have you deleted and recreated the table links in your front end? If 
 
not, that could be a very likely cause of the crash on the 
 
particular form. Linked tables in A2K and above cache a whole lot of 
 
information in them that is not updated by merely altering the 
 
connect string, or by replacing the back end that they were created 
 
for with a completely new one. It could be that there is cached 
 
metadata about the back end that has been invalidated in the process 
 
of recreating the replica. 
 
This seems to me like a much likelier cause of this kind of error 
 
than complex relationships (though the metadata may be in some way 
 
related to the RI issues). 
 
-- 
 
David W. Fenton                  http://www.dfenton.com/ 
 
usenet at dfenton dot com    http://www.dfenton.com/DFA/

Thanks much!  I'll forward this on. 
 
"David W. Fenton" <XXXusenet@dfenton.com.invalid> wrote in message 
 
news:Xns981BD93138320f99a49ed1d0c49c5bbb2@127.0.0.1...