Not seen it, but I'm not up to date with releases. Can you map the user IDs
through UV.LOGINS ?
- Original Message -
From: David Jordan [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] problem with SQL Users
Date: Thu, 3 Apr 2008 15:05:42 +1100
I just
Hi
I have a subroutine that WRITESEQ to a record in a type 1 file called
INTEGRITY.
Is there anyway I can open the file once (in the subroutine) and thereafter
use the same file handle (to avoid opening the file each time the subroutine
is called) ?
All the code on this site opens the file in
Sure You can
and You don't have to have the named common in any other routine.
The only gotcha I'm aware of is that the file stays open until you
exit universe
or explicitely closes it
i.e. even if you LOGTO another acoount. It's quite confusing and
potentially dangerous
that the open file
quote who='Dennis Bartlett' date='Thursday 03 April 2008'
Hi
I have a subroutine that WRITESEQ to a record in a type 1 file called
INTEGRITY.
Is there anyway I can open the file once (in the subroutine) and thereafter
use the same file handle (to avoid opening the file each time the
And - as a suggestion - as mentioned earlier - the array of file names
should contain ACCOUNT-FileName to ensure MainAcct-CustFile #
TestAcct-CustFile -- it's happened more than once the DIM'd array of file
handles survived a LOGTO and suddenly that person is trashing the MAIN
account data
Here is a simple but effect way to handle this scenario:
COMMON /NAMED_COM/ NAMED_COM.REC(10)
EQUATE NAMED_COM.FLAG TO NAMED_COM.REC(1)
EQUATE F.OPEN.FILETO NAMED_COM.REC(2)
Etc.
IF NAMED_COM.FLAG NE @WHO:@DATE THEN
;* Open Files, Set Variables and NAMED_COM.FLAG if everything is OK.
All,
We're running Unidata version 7.1, and are trying to get a pc-based id card
system (Idworks) to communicate via ODBC to our database; we are having
limited success. The software vendor said they thought it was a Unicode
compliance issue. I've found some marketing docs for U2 which
Note, I've researched it in the past but not actually done it, so I may get
something wrong here.
This I do know, however: Unicode is not the default for Unidata. Note that
some of the default MultiValue system delimiters conflict with Unicode
characters. In addition to turning this on and
I could be all wet here, but it is my recollection that while Universe uses
Unicode, Unidata uses UTF-8 for I18N.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
I'm responding to the other responses, to some degree...
Most MultiValue systems are data transparent; what goes in comes out.
Except for the special characters in MV, which I believe are decimal 252
and up. However, in contradiction to an earlier response, these characters
are not used in
All,
Thanks for the information you've provided. We've received some additional
comments from the Id Works vendor. They have indicated that the earlier
versions of their software only required ODBC compliance (with various
conformance levels: core, extended grammar, etc.), but that the current
What ODBC driver are you using? Is this Id Works using Unidata ODBC to retrieve
data from Unidata?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Drew Henderson
Sent: Thursday, April 03, 2008 3:28 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2]
Hey all,
I am pretty sure this is a out of memory/stack space type error but
I was hoping someone could tell me where I can find the fault types and
if there is a way to use the address that the error returned to get
where the code was when it blew up?
below is the error
Abnormal
Hi Ray
Mapping in UV.LOGINS does not help. UV_USERS has domain\user, and if you
type WHO, you get DOMAIN\user, the difference being casing. There is no way
to force the login to be in lower case and no way to change UV_USERS as I am
not a valid SQL User.
UniVerse has made NT AUTHORITY\System
In the UniVerse Administration guide (admin.pdf). Did you have a look or
you can't find them? The documentation isn't the best!!
These errors are best reported to IBM U2 Support. Especially, if you can
reproduce the problem.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
15 matches
Mail list logo
