>>> [EMAIL PROTECTED] 09/17/02 11:45AM >>> From memory, there was a 64 field limit on dBASEIII type .dbf files but the most relevant limitation I'm aware of is the 2k limit on the length of Sambar <RCQ> tag. I believe that includes the format as well...
HTH Ray sqlAt 04:26 AM 17/09/2002, you wrote: >I'm doing an INSERT INTO on a dbf table. Is there a limit on the number >of table columns that can be populated within the same sql statement? Thanks Ray. I'm using dBase IV and the limitiations on the number of fields is 255. The problem lies with Sambar. After digging a little more I found an a 2 year old discussion on this issue, and was able to resolve my problem with this info. Below is the quoted discussion. Subject: RE: [sambar] Insert Statment num of Char. Date: Fri, 13 Oct 2000 10:55:34 -0700 (PDT) From: Jeroen vd Berg <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] A workaround for this problem is to split the insert statement into 2 (or more) parts. First, use an insert statement to insert a piece of the data, then use an update statement to put in the rest of the data. I use it on a few pages where a lot of data is processed and it works okay. Regards, Jeroen --- Dave Goode <[EMAIL PROTECTED]> wrote: > This is the case and a right pain in the **** it is, > too. The buffer for > parsing SQL is 4KB - data above 4096 bytes is > truncated causing your INSERT > to fail. Tod, if you're listening, how about a > user-configurable SQL buffer? > Or a dynamically allocated buffer that will parse > whatever we throw at it? > > Keff, if you want your SQL statements to be larger > than 4096 bytes (parsed - > not unparsed), you'll have to look elsewhere unless > Tod's got something like > my suggestions up his sleeve. PHP? Perl/CGI? I'm > dreading it, but I'll have > to bite the bullet and go down one of these routes. > The latest version of > PHP has built-in MySQL support which is good for me, > but I don't know about > Access. > > An SQL tip for you - keep your SQL compliant with > SQL86 or SQL92. When you > eventually port your database elsewhere (which is > inevitable if you're using > Access) you'll find life a lot easier if you're not > using vendor-specific > extensions... > > > Dave > > Dave Goode's 'Corner of the Net' > www.davegoode.net > > Russian Orthodox Parish of St Ephraim the Syrian, > Cambridge > www.ephraim.org.uk > > The Institute for Orthodox Christian Studies > www.iocs.cam.ac.uk > > PGP: you have the right to privacy. My public key is > available from any > public key server: Key ID 0xD6323324 or directly > from: > www.davegoode.net/pgp/davepublickey.asc > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > > Edwards, Keff R Contractor/Radian > > Sent: Thursday, October 12, 2000 5:13 PM > > To: '[EMAIL PROTECTED]' > > Subject: [sambar] Insert Statment num of Char. > > > > > > I have a form with a text box... > > I will use an insert command to inpute the text > box contents to an access > > database > > > > how many characters can I transfer using the > insert comand... my > > testing reveals > > only 4000~. > > > > Is this right... > > > > Keff ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
