Martin Reid
mwp.reid at qub.ac.uk
Sat Jan 31 11:41:25 CST 2004
John As before it could be dates? Did you read the upsizing report? It should be saved int he same folder as the MDB file. I always use upsizing pro now before moving anything in an MDB file. Its more than worwth the $100 Martin ----- Original Message ----- From: "John W. Colby" <jwcolby at colbyconsulting.com> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Saturday, January 31, 2004 4:42 PM Subject: RE: [AccessD] Upsizing wizard > Looking at the tables in SQL Server manager, the table structure made it out > there, but no data which leads me to believe perhaps some data field caused > the problem. Any thoughts? > > John W. Colby > www.ColbyConsulting.com > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John W. Colby > Sent: Saturday, January 31, 2004 11:38 AM > To: AccessD > Subject: [AccessD] Upsizing wizard > > > I am trying to upsize a reasonably large database and four tables, two of > which are main tables, failed to upsize (table skipped or export failed). > Does the wizard provide any error log which would point me to the reason for > the failure? > > John W. Colby > www.ColbyConsulting.com > > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >