rowset uneditable when I use the ORDER BY clause?

Thread View: borland.public.intrabuilder.data.sql

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Paul Lin Wed, 18 Feb 1998 00:00

#52

Author: Paul Lin
Date: Wed, 18 Feb 1998 00:00

12 lines
917 bytes

When I use an "ORDER BY" clause in my sql statement, the resulting
rowset from the query object (dBASE) becomes uneditable (error: rowset
is read only).  I've tried calling the beginEdit() function and setting
autoedit property to true, which didn't help.  I can't use indices
because the order criteria is to be specified at runtime.  Does anyone
have other ideas?

thanks in advance,

Paul Lin
Davidson & Associates

Re: rowset uneditable when I use the ORDER BY clause?

#56

Author: Michelle Sintov
Date: Wed, 25 Feb 1998 00:00

22 lines
1372 bytes

I too discovered this last week.  In order to edit the rowset, since I am
only adding records, I deactivate the query prior to editing the table,
change the sql (removing the order by clause), activate the table, add the
new records, save the records, then deactivate the table so I can change the
sql and add the order by clause again.

- Michelle

Paul Lin wrote in message <34EB5CF4.CA22D46D@davd.com>...
>When I use an "ORDER BY" clause in my sql statement, the resulting
>rowset from the query object (dBASE) becomes uneditable (error: rowset
>is read only).  I've tried calling the beginEdit() function and setting
>autoedit property to true, which didn't help.  I can't use indices
>because the order criteria is to be specified at runtime.  Does anyone
>have other ideas?
>
>thanks in advance,
>
>Paul Lin
>Davidson & Associates
>

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads