RE: XPOSE4 cur.db error
First of all, let me second Paul's opinion of Xpose4. They have done a
great job with it and we have been able to integrate xpose4 into PDx-Pop
not only on Windows but Linux and Mac OS X as well.
Second, I don't think the issue is the zeros. I just tried it
successfully with 003. It may be a case sensitivity thing and be
looking for capitals? My tables looked like this:
$TABLE ID SID TIME TAD IPRED CL WT APGR NOPRINT ONEHEADER FILE=003.TAB
$TABLE ID CL V NOPRINT ONEHEADER FILE=PATAB003
$TABLE ID WT APGR NOPRINT ONEHEADER FILE=COTAB003
$TABLE ID APGR NOPRINT ONEHEADER FILE=CATAB003
$TABLE ID TIME IPRED IWRES NOPRINT ONEHEADER FILE=SDTAB003
Bill
Quoted reply history
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul Hutson
Sent: Thursday, May 24, 2007 9:33 AM
To: [email protected]
Subject: [NMusers] XPOSE4 cur.db error
I have been getting consistent fatal error messages when I have tried to
bring up NONMEM files set up for evaluation with XPOSE. The text of the
error line varies with what I have asked of XPOSE, but the consistent
component is "cur.db not found". XPOSE 3.1 also had trouble, but more
clearly told me that the file with the requested number was not found.
It turns out that XPOSE at present apparently does not like leading
zeros in the file name. Thus, it was rejecting patab003
but accepting patab3.
Everybody else probably knows this by now. Mats, Andrew, and Justin -
great program. Thanks.
Paul
--
Paul R. Hutson, Pharm.D.
Associate Professor
UW School of Pharmacy
777 Highland Avenue
Madison WI 53705-2222
Tel 608.263.2496
Fax 608.265.5421
Pager 608.265.7000, p7856
_______________________________________________________________________________________________________________________________________