What kind of new characteristic do you have now that involves moving to SQL Server from VFP? Is it something you can't achieve with VFP? I'm curious to know...

Jaime

>Hello all,
>
>Our users using an application written in VFP 6.0 which they used to entering new products with some "fixed" characteristics eg brand, Manufacturer, Color:
>
>Prodid Prodname BRN MAN COLOR
>===========================================
>1 CoCa Cola 330ml COC COC RED
>2 7UP 330 ml 7UP XXX GRE
>
>The form was simple with one grid showing the above data
>Note : The Table was Buffered to 5 and by issuing TABLEUPDATE(.T.) on save all the changes made on the grid thansferred to the original table
>
>
>
>Now I am redesigning the system on (SQL Server 2000) because we have the need to add dynamic characteristics (ie the user to add new characteristics for the specific system)
>
>So I created 2 tables on SQL Server 2000:
>
>Product
>======
>Prodid I
>Name C(40)
>...
>
>
>ProdChr
>========
>Prodid I
>Chrcode C(3)
>ChrVal C(10)
>
>
>The problem is that the user was used to view, enter and edit all the records (of a specific category) and the characteristics and then to save the whole job.
>
>In order to do this now I need to delete all the products of the working category using SPT =sqlexec() and with a loop to insert the whole modified category back. The same with the characteristics so I am using transactions (= SQLSETPROP(nConnHandle, 'Transactions', 2) && Manual transactions
>
>The problem is that I can have 10000 products in a category and 120000 lines in Prodchr to transfer.
>
>This is not so good !
>
>
>Any ideas will be helpful
>
>Note : I tried many designs eg line editing instead of massive editing, edit one characterisic at a time
>(using remote views) etc but I am sure that the users want to see the whole category and edit the all the characteristics and at the end press save.
>
>
>Thanks in advance
>Petros