RE: [U2] Best practice for Sequential IDs using TRANSACTION START COMMIT/RO...

2005-06-16 Thread Bill Haskett
Charles: No, you guys aren't the only ones. This is a pretty miserable hole in the mvDbms functionality. However, since we've been writing this stuff for years the routines are already built to solve our problems. I just didn't know TRANSACTION bracketing was going to break them. Unknowns

RE: [U2] Best practice for Sequential IDs using TRANSACTION START COMMIT/RO...

2005-06-16 Thread Bill Haskett
Clif: Since I've been in both the accounting and information systems fields for over 25 years, I can't say as I understand the term ...non-information content, sequentially assigned, record counter. I'm sure it doesn't mean what I think it does as I've found sequential counters to be an

RE: [U2] Best practice for Sequential IDs using TRANSACTION START COMMIT/R...

2005-06-16 Thread Bill Haskett
Charles: But this doesn't solve the problem of missing sequence numbers if the TRANSACTION doesn't commit. :-( Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Thursday, June 16, 2005 11:57 AM To: u2-users

RE: [U2] Best practice for Sequential IDs using TRANSACTION START COMMIT/R...

2005-06-16 Thread Bill Haskett
Charles: But this doesn't solve the problem of missing sequence numbers if the TRANSACTION doesn't commit. :-( Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Thursday, June 16, 2005 11:57 AM To: u2-users

RE: [U2] Best practice for Sequential IDs using TRANSACTION START COMMIT/R...

2005-06-16 Thread Bill Haskett
Charles: But this doesn't solve the problem of missing sequence numbers if the TRANSACTION doesn't commit. :-( Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Thursday, June 16, 2005 11:57 AM To: u2-users

RE: [U2] Best practice for Sequential IDs using TRANSACTION START COMMIT/R...

2005-06-16 Thread Bill Haskett
Charles: But this doesn't solve the problem of missing sequence numbers if the TRANSACTION doesn't commit. :-( Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Thursday, June 16, 2005 11:57 AM To: u2-users

RE: [U2] Best practice for Sequential IDs using TRANSACTION START COMMIT/R...

2005-06-14 Thread Bill Haskett
Charlie: I wonder if the same issue (transactions don't release record locks until they're committed) applies to the LOCK/UNLOCK statement? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, June 14, 2005 4:25

RE: [U2] Printing from UniVerse

2005-06-06 Thread Bill Haskett
Charlie: It's funny you should raise Microdata. I was taught to never use EQUATEs unless I wanted to create a relationship between both sides of the equation. e.g I'd use the following: EQUATE APFILE$CUSTDATE TO APFILEREC(1) This would allow me to manipulate either side of the equate and know

RE: [U2] Recommendations for reporting tools

2005-06-06 Thread Bill Haskett
Clif and David: Don't let the Raining Data price fool you. Mv.NET will offer the same thing for a ___LOT___ less! I'm testing out SQL Reporting services using ODBC and it works nicely. At this point it's free. I'm going to be testing it with OleDB shortly. Still, at this point it's free or,

RE: [U2] Uniobjects hack

2005-06-01 Thread Bill Haskett
JayJay: Neither one of these verbs are invoked if someone logs onto an account and goes directly to TCL (no menu desired). For instance, one creates a UO account with Q-Pointers, ON.ABORT, and a few other things to allow extraction of data. :-) The two functions you refer to are accessed, I

RE: [U2] Uniobjects hack

2005-05-27 Thread Bill Haskett
Richard: Am I accurate in thinking Pick __USED__ to have file level security but it doesn't exist in the U2 products because, it was always said, the O/S takes care of security (aka: we don't need no stinkin file level security)! Perhaps, having dbms security isn't such a bad idea after all. :-)

<    5   6   7   8   9   10