[AccessD] A2k - BE corruption???

If the client is using something older than Jet SP3, that may be the
source of your problem.  Get them updated to at least SP6.  Otherwise,
there are a bunch of gotchas that may "corrupt" your data.  The versions
of Office don't matter so much as long as A2k is running on both.  Are
both versions of A2k patched to the same SR level?

Charlotte Foust

-----Original Message-----
From: Carlos Alberto Alves [mailto:caa at highway.com.br] 
Sent: Monday, November 03, 2003 4:22 PM
To: AccessD List
Subject: [AccessD] A2k - BE corruption???


Dear Mates:
I would like to have your opinion on this matter. I developed an A2k 
database system with three identical FE's and one BE. It has data from 
jan2001 to now. Upon executing a simple select query I noticed that I 
could not retrieve any records from 2002. The same query executed on a
BE 
backup copy from jul2003 returned all due records.
Is this a BE corruption??? I tried "Compact and repair...", JetComp and 
import all tables to a new BE with no better results.
Things that called my attention:
1- I use Jet 4.0 SP6 and my client uses something older than SP3;
2- I use Access 2000/Office 2000 and my client uses Access 2000/Office
97. Thanks for any input,
-- 
**************************************
* Carlos Alberto Alves               *
* Child Neurologist                  *
* Systems Analyst/Programmer         *
* Rio de Janeiro, Brazil             *
* mailto:caa at highway.com.br          *
**************************************
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com