Darryl Collins
darryl at whittleconsulting.com.au
Sun Mar 18 18:55:11 CDT 2012
Oh hell yeah, I agree with that, Even using the wizard method on default is darn risky. I have seen plenty of instances where fields that should be read as doubles have all be clipped to integers (without any warning too I might add) and caused all sort of errors. I know Excel is a big one for guessing as well. It gets it wrong plenty of times too - annoying IMHO... -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms Sent: Monday, 19 March 2012 10:32 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Not all values paste from Excel to Access I agree with William. This was poorly implemented...especially because there is no SETTING to override this behavior. Access is looking at the first x rows and then making a data conversion on that numeric column.... And it's then expecting all rows to follow as the same data type. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com