Hi, we used to hear a lot about people migrating to SQL Server 'cos they'd hit Fox's 2Gb limit - I've just hit a much lower limit in SQL:
A user for a system I'm prototyping has set up a lot of data in Excel - I have tried everything to import this to SQL without success: I keep getting a "data has exceeded buffer size" error. The trouble is that the user has 'cut and paste'd huge chunks of data into some Excel cells (well over the agreed design limits but I was hoping to trim it later). I tried setting the target table columns to 4095 or 8000 but then I get warnings that I will likely exceed the maximum rowsize of 8000 (doesn't seem very big! - just 4 x 2kb fields) So in desperation I tried setting the target table columns to 'text' - same problem. I can sidestep the problem by using Excel to convert to .csv or dBaseIII but this limits all columns to 257 (?) How do other people handle large text items in SQL Server? Andrew Davies MBCS CITP - AndyD 8-)# ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. Please contact [EMAIL PROTECTED] with any queries. ********************************************************************** _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
