Henry That is a really really bad idea.
Each UniVerse keeps its lock table in memory, used to coordinate access at the group level whilst reading and writing as well as the record lock handling. As soon as you access a file on another system without coordinating with the remote lock table, you are just begging for database corruption. If you are going to do this there is a product called uvNet that coordinates the activity on both ends. Or make up a uniobjects connection from your dev box and copy across that. Or open the remote box as an ODBC source. Or write a simple middleware pipe. But you must must ensure that the write is done by the remote universe, not by your universe against a share. Brian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Martel, Henry > Sent: 12 May 2008 18:59 > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] Blink Error - Dictionary Related > > I have a situation were I have a Prod box and a Dev Box both > with Universe installed. > > On the Prod box we have a samba share that is pointing to the > Dev box and we have voc entries pointing to Dev files. > > But when I execute a command such as: Copy from <file> to Test.<file> > > The records will copy over to the Dev box, but it always > results in a Blink error. > > Has anyone experienced this or know how to fix it? > > Henry M. > Database Administrator > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bessel, Karen > Sent: Friday, May 09, 2008 3:57 PM > To: u2-users@listserver.u2ug.org > Subject: [U2] Blink Error - Dictionary Related > > A client is experiencing a blink error when using a certain > I-descriptor in a SORT, but not in a LIST or SELECT. > > > > I can't copy the code into the post because of copyright > purposes, but this is the dictionary item: > > > > 0001: I > > 0002: IF CASE.PERSON.ID # "" THEN > SUBR("CJ.READ.PERSON",CASE.PERSON.ID,1,"") E > > LSE "" > > 0003: S;*;"*** No Defendant ***" > > 0004: Defendant > > 0005: 30L > > 0006: S > > > > The dictionary item referenced by the I-descriptor: > > > > 0001: A > > 0002: 1 > > 0003: CASE.PERSON.ID > > 0004: > > 0005: M > > 0006: > > 0007: > > 0008: > > 0009: R > > 0010: 8 > > 0011: > > 0012: COMMON > > > > Attribute 1 should be single-valued but there are 27 records > in this file that have multiple values in this field. On our > in-house system, we also have a handful of records that have > multiple values in this field, and I can't recreate the problem here. > > > > There are commons involved in the subroutine referenced by > the I-descriptor. > > > > This issue just came to me and the people who worked on it > before did all of the data related things I would have done: > searched for control characters, fix tool, deleted the file > then recreated it, etc. > > > > I don't know if I've provided enough information to explain > the problem....but has anyone seen this? If you've > experienced an application-related blink error, I'd be > interested in hearing from you. > > > > > > > > > > > > > > > > > > Karen Bessel > Software Developer > > Tyler Technologies, Inc. > 6500 International Parkway, Suite 2000 > Plano, TX 75093 > Phone: 972.713.3770 ext:6227 > Fax: 972.713.3777 > Email: [EMAIL PROTECTED] > Web: http://www.tylertech.com > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
