XPOSE4 cur.db error

Title: Paul R 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

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

Dear Paul, Thanks for the praise. I'd just like to point out that Niclas Jonsson is the main architect around the changes - least credit should go to me. Best regards, Mats Mats Karlsson, PhD Professor of Pharmacometrics Div. of Pharmacokinetics and Drug Therapy Dept. of Pharmaceutical Biosciences Faculty of Pharmacy Uppsala University Box 591 SE-751 24 Uppsala Sweden phone +46 18 471 4105 fax +46 18 471 4003 [EMAIL PROTECTED] _____

Hi Paul, Thanks for the comments. I was wondering if, when you ask Xpose to read the files, you ask it to read run number '3' or '003'. I think the later should work if your files are named 'sdtab003' for example. -Andy Andrew Hooker, Ph.D. Assistant Professor of Pharmacometrics Div. of Pharmacokinetics and Drug Therapy Dept. of Pharmaceutical Biosciences Uppsala University Box 591 751 24 Uppsala Sweden Tel: +46 18 471 4355 www.farmbio.uu.se/research.php?avd=5 _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Hutson Sent: Thursday, May 24, 2007 5:22 PM Cc: [email protected] Subject: Re: [NMusers] XPOSE4 cur.db error XPOSE team: My apologies and thanks to Niclas as well. The shift to R is welcome. Bill: I tried caps vs lower case, since R (and SPlus) can be sensitive to that unless the source code permits either. I couldn't get it to work with the 003 in either case in either XPOSE31 or 4 (build 5.1). I was using NOPRINT ONEHEADER as well. Curious that yours is working. Maybe it has something to do with the humidity. Paul Bachman, William (MYD) wrote: 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 _____