Outlook Rich Text attachment
Note to Help Desk: Look on the AngelicHost MailScanner in
/home/virtual/site2/fst/var/spool/mail.quarantine/20090313 (message
n2DAH7gu009895).
--
Postmaster
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Does anybody knows how to build XML Schema in Unibasic.
Thanks and appreciate.
Jaweed
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
I need to examine fields for perhaps one thousand part.numbers looking
for tech specs that contain character strings like
MIL
Spec
SPEC
-14 etc
While I can do this with commands like... execute 'SELECT IM WITH
OP.SPEC LIKE ...-14... ', this technique is awkward since I have a few
Maybe create a new dictionary that concatenates the multiple attributes
together, and do UPCASE(), then you can keep your Select statement as
is.
Mark
-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Brutzman, Bill
I would use the UniData ESEARCH verb:
:ESEARCH FILE.NAME
STRING: MIL
STRING: Spec
STRING: SPEC
STRING: -14
STRING:
12 records selected to list 0.
SORT FILE.NAME FIELD1 FIELD2
-Original Message-
From: owner-u2-us...@listserver.u2ug.org
If you want to write an xsd then i would use an xsd authoring tool or just
plain old notepad
If you want to generate an xsd from an xml then again there are authoring
tools that will do this (including visual studio) - there is no function in
databasic to do this ( i don't think i may be wrong
If the search is for whole-words only - i.e. to exclude phrases like
'Special Order Only' then you can set up a dict item like
1: V
2: CONVERT( ,@VM,OP.SPEC)
3:
4: TechSpecWords
5: 20L
6: M
And then do a statement like
SELECT IM WITH OP.SPEC = MILSpecSPEC-14
There's a hardwired limit on the
Ok so you want to accept xml as part of your web service input - this would
be normal and just requires you to define public properties for the returned
class as xml.
I have not seen Tonys video - it may be that he shows you how to do that
there.
The basic structure would be something like :-
In UniBasic I would make a dynamic array of all the possibilities then use
MATCHES.
Example:
*
** Do this in your init routine.
*
SEARCH.STRING=
SEARCH.STRING1, -1 = ...'MIL'...
SEARCH.STRING1, -1 = ...'SPEC'...
SEARCH.STRING1, -1 = ...'-14'...
...
*
** Use it like this.
*
IF
How about the INDEX() function in Unibasic
Brutzman, Bill wrote:
I need to examine fields for perhaps one thousand part.numbers looking
for tech specs that contain character strings like
MIL
Spec
SPEC
-14 etc
While I can do this with commands like... execute 'SELECT IM
I use INDEX for this type search in UniBasic. It returns the starting character
position of the string if found otherwise 0
CASE INDEX(OP.SPEC,'MIL',1) # 0
* ADD IT TO A RECORD
RECORD-1=ID
CASE INDEX(OP.SPEC,'Spec',1) # 0
* ETC
-Original Message-
From: Brutzman, Bill
What we have done when we are going to be looking for the same thing
over and over is to create a dictionary that identifies the data and
nulls it if it doesn't have it. Then you create an INDEX on the
dictionary. Extremely fast.
Like
ED DICT IM CHKPART
1 V
2 IF INDEX(OP.SPEC,MIL,1) THEN OP.SEC
Note that SQL and U2 Query statements ( LIST and SORT ) both allow you to
generate a schema. 'WITHSCHEMA' at the end of the command line will add
the schema to the document. When used with the TO clause it will go to
the _XML_/XML directory.
Please look in the Basic Extensions Manual for more
If you are looking for something quick then create a dict item with the
match criteria you want to search for, the following example is based of
the UniData demo account file TAPES
Add an item:
AE DICT TAPES MTYPE
Top of MTYPE in DICT TAPES, 6 lines, 33 characters.
*--: p
001: I
002: 'C':@VM:'R'
Visual Studio comes with a command-line command called xsd that
will generate an XSD from XML. If you do not have VS you can
download this in the Windows SDK v6.0A.
It should be quite straight-forward to write XML to a Dir (type
1/19), execute xsd, then read the result. If you are on *nix,
you
INDEX... is the ticket. It is kind of bizarre that I have never used
INDEX before.
Thanks to all who responded, bonus points to Jeff and Dave... kudos to
Laura and DAG.
When I started, I thought that I needed an array of prevalent
substrings. Now I see that end-users here will want to do their
Brutzman, Bill wrote:
INDEX... is the ticket. It is kind of bizarre that I have never used
INDEX before.
Thanks to all who responded, bonus points to Jeff and Dave... kudos to
Laura and DAG.
When I started, I thought that I needed an array of prevalent
substrings. Now I see that end-users
David,
Not sure what you need to accomplish, Brian's offer looks promising.
You might also try INPUTIF. I use it in status screens. got the idea from
my days working with computer aided dispatch.
ACT=''
LOOP
INPUTIF YOUR.WISH THEN
BEGIN CASE
CASE UPCASE(YOUR.WISH)
18 matches
Mail list logo