Using DRW to edit rows with multiple columned-index?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I am using the DRW to build a maintenance application. My problem is when I
need three columns to specify uniqueness. When I try to edit a row which has
more than one occurance of a value in the first column, it only allows me to
edit (or delete) the first occurance. The three columns are defined as a
clustered index, unique.

Is this a known "feature" or is there a way to get around it? I have tried
tinkering with the FP generated code (detail.asp) but I can't figure out how
to change the syntax to get anything to work. Using just standard Transact
SQL statements in Query Analyzer works just fine, but that's not a good
approach for the end-user.

Thanks for any help you can provide.
 
The DBRW does not support clustered index
- redesign the DB to not require one or hand code your asp generate a unique selector

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| Hi,
| I am using the DRW to build a maintenance application. My problem is when I
| need three columns to specify uniqueness. When I try to edit a row which has
| more than one occurance of a value in the first column, it only allows me to
| edit (or delete) the first occurance. The three columns are defined as a
| clustered index, unique.
|
| Is this a known "feature" or is there a way to get around it? I have tried
| tinkering with the FP generated code (detail.asp) but I can't figure out how
| to change the syntax to get anything to work. Using just standard Transact
| SQL statements in Query Analyzer works just fine, but that's not a good
| approach for the end-user.
|
| Thanks for any help you can provide.
 
well if I could figure out WHERE in the asp to do that ...
As I said, I can't figure out where in the FP generated code to change the
syntax - it has a bunch of FP-looking stuff in it; when I add to the vanilla
SQL statements the retrieval actually stops working entirely. What does one
change?
 
You remove All the DBRW code and hand code All the ASP
Start at http://www.w3schools.com/asp/default.asp

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| well if I could figure out WHERE in the asp to do that ...
| As I said, I can't figure out where in the FP generated code to change the
| syntax - it has a bunch of FP-looking stuff in it; when I add to the vanilla
| SQL statements the retrieval actually stops working entirely. What does one
| change?
|
| "Stefan B Rusynko" wrote:
|
| > The DBRW does not support clustered index
| > - redesign the DB to not require one or hand code your asp generate a unique selector
| >
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| > http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| > _____________________________________________
| >
| >
| > | Hi,
| > | I am using the DRW to build a maintenance application. My problem is when I
| > | need three columns to specify uniqueness. When I try to edit a row which has
| > | more than one occurance of a value in the first column, it only allows me to
| > | edit (or delete) the first occurance. The three columns are defined as a
| > | clustered index, unique.
| > |
| > | Is this a known "feature" or is there a way to get around it? I have tried
| > | tinkering with the FP generated code (detail.asp) but I can't figure out how
| > | to change the syntax to get anything to work. Using just standard Transact
| > | SQL statements in Query Analyzer works just fine, but that's not a good
| > | approach for the end-user.
| > |
| > | Thanks for any help you can provide.
| >
| >
| >
 
Back
Top