Adobe Dreamweaver Forums



Last 10 THreads :         Insert "Search" in a Topic (Last Post : jimpr - Replies : 0 - Views : 1 )           »          Drop Down Sub Buttons (Last Post : 85kris - Replies : 0 - Views : 1 )           »          Spry Accordion Panel Default State All Closed? (Last Post : Steven_K - Replies : 0 - Views : 1 )           »          A question for the gurus (Last Post : bmilesp - Replies : 0 - Views : 1 )           »          This Tough Economy and Flex/AIR (Last Post : Amy Blankenship - Replies : 1 - Views : 2 )           »          Stitching Images Together - Panoramic Views (Last Post : Jim Babbage .:CMX:. & .:Adobe Community Expert:. - Replies : 3 - Views : 4 )           »          ANN: Contact Form Solution Pack (Last Post : Joseph Lowery - Replies : 3 - Views : 4 )           »          Page Layout (Last Post : swif mcvay - Replies : 7 - Views : 8 )           »          cfwindow bug when more than one on page (Last Post : lchalnick - Replies : 0 - Views : 1 )           »          Flex and ColdFusion web services (Last Post : projectproofing - Replies : 0 - Views : 1 )           »         


Home Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
User Info Statistics
Go Back   Adobe Dreamweaver Forums > Dreamweaver: Main > Dreamweaver Application Development
 
Tags: ,



Reply
  #1 (permalink)  
Old 06-02-2008, 03:20 PM
Andy
 
Posts: n/a
Diggs:
Default too many fields

I'm getting this error message when trying to do an update.
I do have a lot of fields to update which is why im getting the error i
guess, but how do i fix it??
Im using ASP classing and Access 2003 Database
Thanks
Andy

Microsoft JET Database Engine (0x80004005)
Too many fields defined.




Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 06-02-2008, 03:20 PM
David Powers
 
Posts: n/a
Diggs:
Default Re: too many fields

Andy wrote:
> Microsoft JET Database Engine (0x80004005)
> Too many fields defined.


Google "too many fields defined". You'll find lots of help.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/
Reply With Quote
  #3 (permalink)  
Old 06-03-2008, 01:07 PM
Andy
 
Posts: n/a
Diggs:
Default Re: too many fields

How do i break up my update in dreamweaver so Access is happy??
I can't normalise the database anymore as all of the fileds are required and
not duplicated.

Thanks
Andy

"Andy" <andy@work.com> wrote in message
news:g235hl$nrc$1@forums.macromedia.com...
> Thanks Dave -
> I decided to do the Update in two parts using the 'command' option in
> Dreamweaver. As far as i can see, the code below is correct. I'm not
> getting any red ! showing in the 'Server Behaviours'.
> When i submit the page to update the database, the page simple
>
>
> ----------
>
>
>
>
>
> "David Powers" <david@example.com> wrote in message
> news:g20lv0$s8g$1@forums.macromedia.com...
>> Andy wrote:
>>> Microsoft JET Database Engine (0x80004005)
>>> Too many fields defined.

>>
>> Google "too many fields defined". You'll find lots of help.
>>
>> --
>> David Powers, Adobe Community Expert
>> Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
>> Author, "PHP Solutions" (friends of ED)
>> http://foundationphp.com/

>
>



Reply With Quote


  #4 (permalink)  
Old 06-03-2008, 01:07 PM
Andy
 
Posts: n/a
Diggs:
Default Re: too many fields

Thanks Dave -
I decided to do the Update in two parts using the 'command' option in
Dreamweaver. As far as i can see, the code below is correct. I'm not getting
any red ! showing in the 'Server Behaviours'.
When i submit the page to update the database, the page simple


----------





"David Powers" <david@example.com> wrote in message
news:g20lv0$s8g$1@forums.macromedia.com...
> Andy wrote:
>> Microsoft JET Database Engine (0x80004005)
>> Too many fields defined.

>
> Google "too many fields defined". You'll find lots of help.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
> Author, "PHP Solutions" (friends of ED)
> http://foundationphp.com/



Reply With Quote
  #5 (permalink)  
Old 06-03-2008, 03:35 PM
David Powers
 
Posts: n/a
Diggs:
Default Re: too many fields

Andy wrote:
> How do i break up my update in dreamweaver so Access is happy??
> I can't normalise the database anymore as all of the fileds are required and
> not duplicated.


I don't know. I haven't used Access for at least five years. If you
can't normalize your database, it sounds as though there's a serious
problem with the way you have designed it.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/
Reply With Quote
  #6 (permalink)  
Old 06-03-2008, 03:35 PM
Philo
 
Posts: n/a
Diggs:
Default Re: too many fields


Just how many fields do you have?
Reply With Quote


  #7 (permalink)  
Old 06-03-2008, 03:35 PM
Andy
 
Posts: n/a
Diggs:
Default Re: too many fields

Thanks for replying....
There are about 160 fields, all of which are needed.
They will hold the data for test results.

-----------

<%

if(Request("CertNo") <> "") then Update1__ins1 = Request("CertNo")

if((RSinstrument.Fields.Item("InstrumentID").Value ) <> "") then
Update1__MMColParam1 = (RSinstrument.Fields.Item("InstrumentID").Value)

if(Request.QueryString("HistID") <> "") then Update1__MMColParam2 =
Request.QueryString("HistID")

if(Request("checkboxUsed") <> "") then Update1__ins2 =
Request("checkboxUsed")

if(Request("Cont_App1") <> "") then Update1__ins4 = Request("Cont_App1")

if(Request("Cont_App2") <> "") then Update1__ins5 = Request("Cont_App2")

if(Request("Cont_App3") <> "") then Update1__ins6 = Request("Cont_App3")

if(Request("Cont_PF1") <> "") then Update1__ins7 = Request("Cont_PF1")

if(Request("Cont_PF2") <> "") then Update1__ins8 = Request("Cont_PF2")

if(Request("Cont_PF3") <> "") then Update1__ins9 = Request("Cont_PF3")

if(Request("Cont_Read1") <> "") then Update1__ins10 = Request("Cont_Read1")

if(Request("Cont_Read2") <> "") then Update1__ins11 = Request("Cont_Read2")

if(Request("Cont_Read3") <> "") then Update1__ins12 = Request("Cont_Read3")

if(Request("Cont_TN1") <> "") then Update1__ins13 = Request("Cont_TN1")

if(Request("Cont_TN2") <> "") then Update1__ins14 = Request("Cont_TN2")

if(Request("Cont_TN3") <> "") then Update1__ins15 = Request("Cont_TN3")

if(Request("Cont_Tol1") <> "") then Update1__ins16 = Request("Cont_Tol1")

if(Request("Cont_Tol2") <> "") then Update1__ins17 = Request("Cont_Tol2")

if(Request("Cont_Tol3") <> "") then Update1__ins18 = Request("Cont_Tol3")

if(Request("cross_checked") <> "") then Update1__ins19 =
Request("cross_checked")

if(Request("CurrentAC_App1") <> "") then Update1__ins21 =
Request("CurrentAC_App1")

if(Request("CurrentAC_App2") <> "") then Update1__ins22 =
Request("CurrentAC_App2")

if(Request("CurrentAC_App3") <> "") then Update1__ins23 =
Request("CurrentAC_App3")

if(Request("CurrentAC_TN1") <> "") then Update1__ins24 =
Request("CurrentAC_TN1")

if(Request("CurrentAC_TN2") <> "") then Update1__ins25 =
Request("CurrentAC_TN2")

if(Request("CurrentAC_TN3") <> "") then Update1__ins26 =
Request("CurrentAC_TN3")

if(Request("CurrentAC_PF1") <> "") then Update1__ins27 =
Request("CurrentAC_PF1")

if(Request("CurrentAC_PF2") <> "") then Update1__ins28 =
Request("CurrentAC_PF2")

if(Request("CurrentAC_PF3") <> "") then Update1__ins29 =
Request("CurrentAC_PF3")

if(Request("CurrentAC_Read1") <> "") then Update1__ins30 =
Request("CurrentAC_Read1")

if(Request("CurrentAC_Read2") <> "") then Update1__ins31 =
Request("CurrentAC_Read2")

if(Request("CurrentAC_Read3") <> "") then Update1__ins32 =
Request("CurrentAC_Read3")

if(Request("CurrentAC_Tol1") <> "") then Update1__ins33 =
Request("CurrentAC_Tol1")

if(Request("CurrentAC_Tol2") <> "") then Update1__ins34 =
Request("CurrentAC_Tol2")

if(Request("CurrentAC_Tol3") <> "") then Update1__ins35 =
Request("CurrentAC_Tol3")

if(Request("CurrentDC_App1") <> "") then Update1__ins36 =
Request("CurrentDC_App1")

if(Request("CurrentDC_App2") <> "") then Update1__ins37 =
Request("CurrentDC_App2")

if(Request("CurrentDC_App3") <> "") then Update1__ins38 =
Request("CurrentDC_App3")

if(Request("CurrentDC_TN1") <> "") then Update1__ins39 =
Request("CurrentDC_TN1")

if(Request("CurrentDC_TN2") <> "") then Update1__ins40 =
Request("CurrentDC_TN2")

if(Request("CurrentDC_TN3") <> "") then Update1__ins41 =
Request("CurrentDC_TN3")

if(Request("CurrentDC_PF1") <> "") then Update1__ins42 =
Request("CurrentDC_PF1")

if(Request("CurrentDC_PF2") <> "") then Update1__ins43 =
Request("CurrentDC_PF2")

if(Request("CurrentDC_PF3") <> "") then Update1__ins44 =
Request("CurrentDC_PF3")

if(Request("CurrentDC_Read1") <> "") then Update1__ins45 =
Request("CurrentDC_Read1")

if(Request("CurrentDC_Read2") <> "") then Update1__ins46 =
Request("CurrentDC_Read2")

if(Request("CurrentDC_Read3") <> "") then Update1__ins47 =
Request("CurrentDC_Read3")

if(Request("CurrentDC_Tol1") <> "") then Update1__ins48 =
Request("CurrentDC_Tol1")

if(Request("CurrentDC_Tol2") <> "") then Update1__ins49 =
Request("CurrentDC_Tol2")

if(Request("CurrentDC_Tol3") <> "") then Update1__ins50 =
Request("CurrentDC_Tol3")

if(Request("TargetDate") <> "") then Update1__ins51 = Request("TargetDate")

if(Request("EarthBO_App1") <> "") then Update1__ins52 =
Request("EarthBO_App1")

if(Request("EarthBO_App2") <> "") then Update1__ins53 =
Request("EarthBO_App2")

if(Request("EarthBO_App3") <> "") then Update1__ins54 =
Request("EarthBO_App3")

if(Request("EarthBO_TN1") <> "") then Update1__ins55 =
Request("EarthBO_TN1")

if(Request("EarthBO_TN2") <> "") then Update1__ins56 =
Request("EarthBO_TN2")

if(Request("EarthBO_TN3") <> "") then Update1__ins57 =
Request("EarthBO_TN3")

if(Request("EarthBO_PF1") <> "") then Update1__ins58 =
Request("EarthBO_PF1")

if(Request("EarthBO_PF2") <> "") then Update1__ins59 =
Request("EarthBO_PF2")

if(Request("EarthBO_PF3") <> "") then Update1__ins60 =
Request("EarthBO_PF3")

if(Request("EarthBO_Read1") <> "") then Update1__ins61 =
Request("EarthBO_Read1")

if(Request("EarthBO_Read2") <> "") then Update1__ins62 =
Request("EarthBO_Read2")

if(Request("EarthBO_Read3") <> "") then Update1__ins63 =
Request("EarthBO_Read3")

if(Request("EarthBO_Tol1") <> "") then Update1__ins64 =
Request("EarthBO_Tol1")

if(Request("EarthBO_Tol2") <> "") then Update1__ins65 =
Request("EarthBO_Tol2")

if(Request("EarthBO_Tol3") <> "") then Update1__ins66 =
Request("EarthBO_Tol3")

if(Request("EarthOh_App1") <> "") then Update1__ins67 =
Request("EarthOh_App1")

if(Request("EarthOh_App2") <> "") then Update1__ins68 =
Request("EarthOh_App2")

if(Request("EarthOh_App3") <> "") then Update1__ins69 =
Request("EarthOh_App3")

if(Request("EarthOh_TN1") <> "") then Update1__ins70 =
Request("EarthOh_TN1")

if(Request("EarthOh_TN2") <> "") then Update1__ins71 =
Request("EarthOh_TN2")

if(Request("EarthOh_TN3") <> "") then Update1__ins72 =
Request("EarthOh_TN3")

if(Request("EarthOh_PF1") <> "") then Update1__ins73 =
Request("EarthOh_PF1")

if(Request("EarthOh_PF2") <> "") then Update1__ins74 =
Request("EarthOh_PF2")

if(Request("EarthOh_PF3") <> "") then Update1__ins75 =
Request("EarthOh_PF3")

if(Request("EarthOH_Read1") <> "") then Update1__ins76 =
Request("EarthOH_Read1")

if(Request("EarthOH_Read2") <> "") then Update1__ins77 =
Request("EarthOH_Read2")

if(Request("EarthOH_Read3") <> "") then Update1__ins78 =
Request("EarthOH_Read3")

if(Request("EarthOh_Tol1") <> "") then Update1__ins79 =
Request("EarthOh_Tol1")

if(Request("EarthOh_Tol2") <> "") then Update1__ins80 =
Request("EarthOh_Tol2")

if(Request("EarthOh_Tol3") <> "") then Update1__ins81 =
Request("EarthOh_Tol3")

if(Request("FlashT_App1") <> "") then Update1__ins82 =
Request("FlashT_App1")

if(Request("FlashT_App2") <> "") then Update1__ins83 =
Request("FlashT_App2")

if(Request("FlashT_App3") <> "") then Update1__ins84 =
Request("FlashT_App3")

if(Request("FlashT_TN1") <> "") then Update1__ins85 = Request("FlashT_TN1")

if(Request("FlashT_TN2") <> "") then Update1__ins86 = Request("FlashT_TN2")

if(Request("FlashT_TN3") <> "") then Update1__ins87 = Request("FlashT_TN3")

if(Request("FlashT_PF1") <> "") then Update1__ins88 = Request("FlashT_PF1")

if(Request("FlashT_PF2") <> "") then Update1__ins89 = Request("FlashT_PF2")

if(Request("FlashT_PF3") <> "") then Update1__ins90 = Request("FlashT_PF3")

if(Request("FlashT_Read1") <> "") then Update1__ins91 =
Request("FlashT_Read1")

if(Request("FlashT_Read2") <> "") then Update1__ins92 =
Request("FlashT_Read2")

if(Request("FlashT_Read3") <> "") then Update1__ins93 =
Request("FlashT_Read3")

if(Request("FlashT_Tol1") <> "") then Update1__ins94 =
Request("FlashT_Tol1")

if(Request("FlashT_Tol2") <> "") then Update1__ins95 =
Request("FlashT_Tol2")

if(Request("FlashT_Tol3") <> "") then Update1__ins96 =
Request("FlashT_Tol3")

%>





"Philo" <meansyou@nospam.net> wrote in message
news:g23f2g$4ea$1@forums.macromedia.com...
>
> Just how many fields do you have?



Reply With Quote
  #8 (permalink)  
Old 06-04-2008, 02:24 PM
Philo
 
Posts: n/a
Diggs:
Default Re: too many fields

I am with David, you have a desgin problem. I see a whole series of 1,
2 & 3 on your field names. That means there should be a way to
normalize that where you would have 3 records, one for each of the
numbers 1 thru 3.

A 160 fields to complete on a form seems like a huge time consuming
task for a user to complete. There should be someway for the user to
break it up and from what little I can see it looks like it could be
broken into thirds.

I would also consder changing to MSSQL. Access is slow and prone to
many problems including corrupted files.
Reply With Quote
  #9 (permalink)  
Old 06-05-2008, 01:12 PM
Andy
 
Posts: n/a
Diggs:
Default Re: too many fields

Thanks Guys
Each of the fields is a possible reading from a test result. Not all fields
need to van a value, but the option has to be available.
For instance, the user would enter his/her test results in to the relevant
text fields. Not all results will have all values.
Each text field is a unique reading and not duplicated in the database.
I should be using MSSQL i know, but i have yet to make the leap and my
knowledge is limited where MSSQL is concerned.

Thanks for the advice

Andy




"Philo" <meansyou@nospam.net> wrote in message
news:g260c5$32l$1@forums.macromedia.com...
>I am with David, you have a desgin problem. I see a whole series of 1,
> 2 & 3 on your field names. That means there should be a way to
> normalize that where you would have 3 records, one for each of the
> numbers 1 thru 3.
>
> A 160 fields to complete on a form seems like a huge time consuming
> task for a user to complete. There should be someway for the user to
> break it up and from what little I can see it looks like it could be
> broken into thirds.
>
> I would also consder changing to MSSQL. Access is slow and prone to
> many problems including corrupted files.



Reply With Quote


  #10 (permalink)  
Old 06-05-2008, 01:12 PM
Dooza
 
Posts: n/a
Diggs:
Default Re: too many fields

Andy wrote:
> Thanks Guys
> Each of the fields is a possible reading from a test result. Not all fields
> need to van a value, but the option has to be available.
> For instance, the user would enter his/her test results in to the relevant
> text fields. Not all results will have all values.
> Each text field is a unique reading and not duplicated in the database.
> I should be using MSSQL i know, but i have yet to make the leap and my
> knowledge is limited where MSSQL is concerned.
>
> Thanks for the advice


You would have the same problem with MSSQL, as its ADO that has the
field limit, not the database.

Steve
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



© Camley Interactive (camley.info) 2008 - all logos and images are copywrite their respective owners.
Proud member of the Camley Interactive Network
All times are GMT. The time now is 05:36 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.1.0 ©2007, Crawlability, Inc.
Inactive Reminders By Mished.co.uk