| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 729.1 | | SAC::JOYCE | Going Down-Under and I don't give a XXXX | Wed May 20 1992 18:07 | 9 |
| re .-1
that was a typo, it should have read...
<FORM AUTO SELECT FOR DOCDB WITH .%WHOLE NES "" DO SEL_STYLE/etc. etc.
Andy
|
| 729.2 | This has taken a long time to surface | IOSG::MAURICE | A few follicles short | Wed May 20 1992 18:53 | 7 |
| Hi,
I've followed the code and it's a bug in the DOCDB action routine. And
it's in V3.0 as well. It looks like it's always been there and gone
unnoticed.
Stuart
|
| 729.3 | | SAC::JOYCE | Leaving... and I don't give a XXXX | Thu May 21 1992 11:48 | 9 |
|
Re .-1
Stuart,
Is it just .%WHOLE or any other fields (.%KEY springs to mind?)
(I guess I could try this but I'm lazy...)
Andy
|
| 729.4 | | SAC::JOYCE | Leaving... and I don't give a XXXX | Thu May 21 1992 11:52 | 6 |
| I just tried...
<for docdb do get oa$display = .%key \\ force
...and all I get is blanks 8(
|
| 729.5 | Even the XXXX field! | IOSG::MAURICE | A few follicles short | Thu May 21 1992 12:19 | 9 |
| Andy,
Any other fields I'm afraid. Perhaps you could give some details of
what your application is trying to achieve, so that possibly we could
suggest an alternative strategy.
Cheers
Stuart
|
| 729.6 | | SAC::JOYCE | Leaving... and I don't give a XXXX | Thu May 21 1992 12:56 | 25 |
|
re .-1
> Any other fields I'm afraid. Perhaps you could give some details of
> what your application is trying to achieve, so that possibly we could
> suggest an alternative strategy.
It's actually a "support tool"; an arg form into which you enter the
name of a dataset, optional alternate k-o-r, an optional rse, optional
fields to display etc.etc. and it goes away and builds a SELECT FOR..
and displays the output to the screen or to a file. If the user does
not enter in an RSE it actaully uses "WITH .%WHOLE NES ''". I can work
around this but the other problem is that, if the user does not specfiy
which fields they want to display it uses "SEL_STYLE .%WHOLE" to output
the whole record. Obviously I don't want to hard-code any field names
in as this is supposed to be a generic tool for any entry form dataset.
I realise that under V3.0 I could probably use the OA$FORM_INFO dsab
but this is on V2.4. DOCDB is a dataset that they search quiet a lot
for one reason or another (usually trying to sort pout screwed up
account transfers!)
Andy
Andy
|
| 729.7 | FOR loops don't work with DOCDB dataset. | FAILTE::LAAHS | An accumulation of Celts | Fri May 22 1992 14:27 | 9 |
| Andy,
I think you will find that DOCDB does not support the necessary action
routines to perform a FOR loop. In my experience it's always been like
this so even if you were allowed to get to the fields you require it
probably won't be enough.
FWIW,
Kevin
|
| 729.8 | | SAC::JOYCE | Leaving... and I don't give a XXXX | Fri May 22 1992 19:17 | 7 |
|
But surely, DOCDB is just an entry form isn't it? What's the difference
between it and PROFIL?
If it was CAB$ that I was havinf a problem with I'd understand...
|
| 729.9 | Non-standard | IOSG::MAURICE | A few follicles short | Fri May 22 1992 19:27 | 8 |
| Re .8
No - both DOCDB and PROFIL are both "special" entry forms where there
is Bliss code underneath to interpret the actions. For example in the
Profile action there is special code so that only administrators can
update certain fields in the record.
Stuart
|
| 729.10 | DOCDB is very strange (or even special) | SIOG::T_REDMOND | Thoughts of an Idle Mind | Sat May 23 1992 21:42 | 6 |
| Right, and in V3.0 DOCDB becomes even more special. Those that doubt
this statement should call up the form on screen and press GOLD/V. All
of a sudeen you see fields that count up to considerably more than the
500 bytes record length known by RMS...
Tony
|