RE: [U2] Named Common Issues in UV

2005-01-11 Thread Richard Taylor
I used UV subroutines extensively from VB6 and never had any problems. I am not sure at this point how named common was used in that area. I can tell you that my previous company tried to use named common in a manner similar to what you are trying, but this was in straight UV programming. We

Unclassified RE: [U2] Named Common Issues in UV

2005-01-11 Thread HENDERSON MIKE, MR
Dick, We use named commons extensively in UniBasic programs called from the database layer (COM components, written in VB6 using the UniObjects interface) of our web applications. One of the principal uses is to hold file handles, as you illustrated, except that we keep up to 650 files open that

RE: [U2] Named Common Issues in UV

2005-01-11 Thread Alfke, Colin
In UniData (not sure about UniVerse) the named common name is only significant for the first 7 digits. So your VBNOTEPAGE3 will be the same as VBNOTEPAGE1. IE. you may think the name is unique but the system doesn't. The name looks like there might be others with a similar name so this could be

RE: Unclassified RE: [U2] Named Common Issues in UV

2005-01-11 Thread Bob Woodward
PROTECTED] On Behalf Of HENDERSON MIKE, MR Sent: Tuesday, January 11, 2005 11:19 AM To: u2-users@listserver.u2ug.org Subject: Unclassified RE: [U2] Named Common Issues in UV Dick, We use named commons extensively in UniBasic programs called from the database layer (COM components, written in VB6

RE: [U2] Named Common Issues in UV

2005-01-11 Thread David Jordan
We have used named common in subroutines called from UV Basic to hold file variables and dimensioned file variables without problems for over 5 years. There was a quirk, if I remember right, that I had to play around with the common. I remember reducing the number of items to a named common and

RE: [U2] Named Common Issues in UV

2005-01-11 Thread Kryka, Richard
Colin Alfke wrote: In UniData (not sure about UniVerse) the named common name is only significant for the first 7 digits. So your VBNOTEPAGE3 will be the same as VBNOTEPAGE1. IE. you may think the name is unique but the system doesn't. The name looks like there might be others with a similar

RE: [U2] Named Common Issues in UV

2005-01-11 Thread Stevenson, Charles
Richard, Besides the 7 character name limit, here's another scenario that would cause grief. Don't know if it applies to you. It has nothing particularly to do with VB. Consider a single session that LOGTOs different accounts: 1. VBNOTEPAGE3 successfully runs in account A. common is

RE: [U2] Named Common Issues in UV

2005-01-11 Thread Rick Ramsey
Healthpac Computer Systems, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jordan Sent: Tuesday, January 11, 2005 3:02 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Named Common Issues in UV We have used named common in subroutines called

RE: [U2] Named Common Issues in UV

2005-01-11 Thread Rick Ramsey
. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jordan Sent: Tuesday, January 11, 2005 3:02 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Named Common Issues in UV We have used named common in subroutines called from UV Basic to hold file

RE: Unclassified RE: [U2] Named Common Issues in UV

2005-01-11 Thread HENDERSON MIKE, MR
] On Behalf Of Bob Woodward Sent: Wednesday, 12 January 2005 08:39 To: u2-users@listserver.u2ug.org Subject: RE: Unclassified RE: [U2] Named Common Issues in UV We also use a dimensioned array to hold our file handles. I'm not convinced, personally, that this has much benefit to system performance