![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Ensuring that the export location for a csv export actually exists Topic Summary: Created On: 21-Jul-2008 03:27 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Tony, I cannot thank you enough for your prompt response to my post. I truly appreciate your help!!!! Regards, Pranav | |
![]() |
|
Hi All,
I have created a variant of the in-built "CSV export" script in DOORS. I have basically hidden the user interface and hard-coded all the export options - including the file location of the csv export. I was wondering if there is any DXL function that helps determine of the hard-coded file location is a valid one. I would appreciate it if you could let me know. Thank you. Regards, Pranav |
|
![]() |
|
![]() |
|
You can use stat to check for existance of files and directories.
------------------------- Tony Goodman Smart DXL limited www.smartdxl.com |
|
![]() |
|
![]() |
|
If you want to check that you can write to a file then use this.
bool canOpenFile(string pathname, bool forWrite) Operation Returns true when the file pathname can be opened; otherwise, returns false. If forWrite is set to true, the file is opened for write and the current contents of the file are cleared. If forWrite is set to false the file is opened read only and the existing contents are unchanged. ------------------------- Tony Goodman Smart DXL limited www.smartdxl.com |
|
![]() |
|
![]() |
|
Tony,
I cannot thank you enough for your prompt response to my post. I truly appreciate your help!!!! Regards, Pranav |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.