Kurt,
You can not have FRB report that is ordered by a key. This is true and this is
false. The true because any "key" specified in the file/table schematic of
RunTimeReport procedure will be ignored. The reason is that any particular
report layout based on this VIEW definition can use it's own sort order. To
define sort order in FRB report you have to add one or more "Sorting bands" to
the report layout. Sorting band expression(s) will affect VIEW{Prop:Order}
dynamically at run-time. Clarion database driver will translate it into WHERE
clause of SQL "select" query. MSSQL server engine is smart enough. It uses an
existing key matching the WHERE clause if possible. So, finally, you can have
FRB report that is ordered by a key. And this is because the first settence is
false.
Could you please be more specific what is the problem?
Thank you,
---
Oleg Fomin <oleg@fomin.info>
|