> From: Symeon Breen > A pooling connection goes into 1 single account yes > We have a special "shared" account for the pools with > voc pointers to the real customer accounts. Part of > the message passed to the backend is the customer so > it opens the correct files etc.
Rather than having a pointer in the VOC for every file and using code like this: OPEN "CUSTOMER*":COMPANY TO FCUST ELSE * return error what about this?: CALL GET.PATH.FOR(COMPANY,PATH) OPENPATH PATH:"/CUSTOMER" TO FCUST ELSE... That works with hashed files as well as dir files. That will eliminate the hassle of pointers. (OPENPATH is available for Universe, not UniData, right?) Traditional apps just open the local database file, and generally don't allow for different fiscal entities per account (no COMPANY reference in the filename). As we've seen this has become a real hassle in web integration, even with connection pooling which locks to a single account. But if you're going to modify your app anyway to accommodate using a different pointer for every file, you might as well change OPEN to OPENPATH. Is there any reason why this isn't technically sound? T _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
