XML: Include a Flexible Parser in Your C++ Applications

• Download source - 304.6 KB

Includes:

• XML class source files (XML.CPP , XML.H , MIME.H)
• Documentation (XML.CHM)
• Testing project XMLTEST (cpp/sln/vcproj)
• The following compiled applications: TXML.EXE for Win32 , XMLPPC.EXE for Windows Mobile 5+ devices.
• XDB.CPP, demonstrating the usage of XML library in creating a configuration dialog box.

Introduction

Are you tired of the many non-portable XML solutions around? Try my library. It works in any OS and in any compiler. No MFC, no COM, no global variables, Plain, pure C++!

Features

• Portable, works in any environment -- I've tested it under Microsoft Visual C++ 2005, Borland, GCC, Codewarrior, Pocket PC 2003+ and with Windows, Linux, Windows Mobile and Symbian operating systems
• Class-based manipulation or INI-style wrappers
• UTF-8 and (win32) UTF-16 read/write support
• Import from file, memory, or (Win32) URL
• Read/save encrypted XML files; custom encryption
• Export to file, memory or (Win32) registry key
• Database queries
• Allows XML memory compression
• Tests for integrity
• Allows for "on-the-fly" variable creation and return value
• Element/variable/comment/content creation, removal, sort, moving, comparison
• Allows copy/paste of an XML element to and from Windows Clipboard as text
• Ability to import database using ADO (Win32)
• Supports the &vars;
• Save/load binary data in variables (requires mime.h)
• Supports the CDATA
• Supports element Unloading and Reloading
• XML element updating
• Supports temporal variables
• HTML help
• x64 compatibility

License

Free, for any kind or freeware, shareware, commercial, or whateverware project, as long as you:

• Credit me in your application's documentation and/or the About box
• Register at my forum (http://www.turboirc.com/forum) so you receive updates and news about the library
• Drop me a note via the forum for the name of your application (If it will be released) so I can link to you.

No STL or Exceptions?

STL and exception handling are not available yet in any C++ implementation - for example, no STL exists in Symbian OS SDK. Therefore, I 've decided to use my own Z<> class (which is defined in xml.cpp) in order to manipulate the buffers. Newer versions will include a STL implementation as well.

Manipulating XML Using the Classes

There are 7 classes:

• XML manages the XML file: opens, saves, exports, etc.
• XMLHeader manages the XML header (XML headers can include comments)
• XMLComment manages an XML comment
• XMLContent manages an XML content
• XMLElement manages an XML element
• XMLVariable manages an XML variable
• XMLCData manages an XML custom data

I won't describe all the member functions of these classes because there is already a description in my help file found in the zip. Here, I will demonstrate simple usage of them. Please note that the library doesn't use exception handling or STL because these two are not always found in C++ implementations (i.e. Symbian).

The code below loads an XML file, then checks for integrity and compresses memory. test.xml is the sample file I used. Note that the element/variable names are case sensitive.

XML* a = new XML("f.xml");
// load from file

XML* a = new XML("<blah f="\">",1);
// load from memory from ASCIIZ string
XML* a = new XML("http://www.some.com/files.xml",2);
// load from URL (Win32)

ASSERT(a->IntegrityCheck() == true && a->ParseStatus() == 0);

a->CompressMemory();

//Get 3rd element's name, and its variable "v" value.
//Also set new variable "tz" with normal and with 'on the fly' mode
char y[100] = {0};
a->GetRootElement()->GetChildren()[0]->GetElementName(y);
// now y == "Cfg"

a->GetRootElement()->GetChildren()[0]->FindVariableZ("v")->GetValue(y);
// now y == "Cfg"

// Create "tz" in the 'normal' mode
XMLElement* e = a->GetRootElement()->GetChildren()[0];
XMLVariable* v = new XMLVariable("tz","some value");
e->AddVariable(v);
// now do not delete v, it is owned by e

// Create "tz" on the fly
a->GetRootElement()->GetChildren()[0]->FindVariableZ(
    "tz",true)->SetValue("some value");

// FindVariableZ(x,true) creates the var if doesn't exist!

// Create Comments and Contents in the same way.
// Use 0 instead of y to get the # of bytes required </blah>

// <blah f="\">for the returned string.
// Lets save/export:
if (a->IntegrityTest())
 {
 a->Save(); // Saves back to file
 a->Save("new.xml");
 a->Export(fp,1,0,0);

// Save to a fp. You can also export to memory
// or save only one element by calling XMLElement :: Export.
 delete a;

// bye bye; </blah>
// <blah f="\">Note that the destructor doesn't save the file by default,
//unless you call XML :: SaveOnClose().
 }</blah> 

Manipulating XML Files using INI-Style Wrappers

Instead of WritePrivateProfileString, you now have some INI-style functions:

• XMLSetString
• XMLGetString
• XMLSetInt
• XMLGetInt
• XMLSetBinaryData
• XMLGetBinaryData
• XMLSetFloat
• XMLGetFloat

These functions can work standalone or with an already opened XML object. When a valid XML object is passed to them, they modify it. When a file name is passed to them, they create an XML object, load the file, read/write it and then save it back, pretty much as the INI file functions.

Because these functions accept their elements as a string with \ (for example, Cfg\\Amplify), you can only manipulate XML files that have unique element names. Otherwise, corruption will occur.

Now let's try getting/setting some data to our XML file:

char y[1000] = {0};

XMLGetString("Cfg","v","",y,1000,"test.xml");
    // This gets 'Bowlingy' to y.
XMLGetString("Cfg\\Amplify","V","not_found",y,1000,"test.xml");
    // This gets 'not_found' to y. Variables/Elements are case sensitive!

XMLSetString("A\\B\\C","v","hahaha","test.xml");
    // Elements A B C are created!
Fread(y,1,100,some_file);
XMLSetBinaryData("A\\B\\C","v",y,100,"test.xml");
    // Binary data can be saved/read, encoded with Base64 (mime.h)

Note that all these string functions require a UTF-8 string. In case you are under Windows, you can also call XMLSetString with wchar_t values, which the library automatically converts to UTF-8 by using WideCharToMultiByte.

Unloading and Reloading

Use XMLElement :: UnloadElement, ReloadElement to temporarily save an element to a memory file (check the help file for details). This enables you to manipulate a huge XML file without wasting your RAM.

Soon to implement XML :: PartialLoad().

Item Borrowing

Use XMLElement :: BorrowItem to add a XMLElement* mirror from another XMLElement*. This is an advanced feature that must be used with caution, or you will crash your application with a big nice stack overflow. Read the help file for details.

Temporal Variables

A temporal element is an XMLElement (or an XMLVariable) that simply has the 'temporal' flag on. You can set or query this flag by calling SetTemporal and GetTemporal member functions. By default, elements and variables are not temporal.

You can also create a temporal element or variable by a constructor flag. Also, XMLElement :: FindElementZ() and XMLElement :: FindVariableZ, which can create an element/variable on the fly, can also mark it as temporal.

When you call XMLElement :: RemoveTemporalElements(bool Deep) , all temporal children elements are removed. If Deep is true, all temporal elements of all its children are also removed. If an element is temporal and it is removed, then all children of it are of course removed, even if not marked as temporal. Therefore, marking, say, your root element as temporal will result in the destroyment of the entire XML file when you call RemoveTemporalElements().

When you call XMLElement :: RemoveTemporalVariables(bool Deep), all temporal variables of this element are removed. If Deep is set to true, all temporal variables of all its children are also removed.

When you call XML :: RemoveTemporalElements(), it calls XMLElement::RemoveTemporalElements(true) and XMLElement::RemoveTemporalVariables(true) for the root element.

Note that unless you remove the temporal elements manually using the above functions, they are not removed - they are considered normal elements/variables and they are saved or exported normally.

Using Unicode Strings with the Library

The library works with UTF-8, which means that the strings passed and returned are char*s. In order to pass a Unicode string to the library, you must convert it manually WideCharToMultiByte(CP_UTF8,...);. I have created a very simple wrapper that can do that as a class:

class W
{
public:

W(const wchar_t* x)
{
int y = wcslen(x);
int wy = y*2 + 100;
we = new char[wy];
memset(we,0,wy);

WideCharToMultiByte(CP_UTF8,0,x,-1,we,wy,0,0);
}

~W()
{
delete[] we;
}

operator char* ()
{
return we;
}
};

So if you have a Unicode string x and you want to use it in my library, you would use W(x) instead, which converts your Unicode string to a UTF-8 string, uses it via the operator and the destructor frees it.

64-bit Compatibility

The library is 64-bit compatible; you will be able to compile and use it under any 64-bit compiler without problems.

Element Updating

You will at times need to update a XMLElement with the elements and variables of another element.

int UpdateElement(XMLElement* NewEl,bool UpdateVariableValues = false);

This will:

• Try all variables of NewEl. If any of them also exists in your current element, then if UpdateVariableValues == true, the function will update the variable. If the variable of NewEl does not exist into your element, it is copied.
• Try all elements of NewEl. If any of the elements do not exist in your current element, it is copied. If it exists, then the function calls UpdateElement for that element against the child element of NewEl, resulting in a recursive update of all grand children and variables.

Database Import with ADO

Use XML :: ImportDB() to import a database. You have to mess with two structures:

struct IMPORTDBTABLEDATA
   {
   char name[256];
   char itemname[100];
   int nVariables;
   char** Variables;
   char** ReplaceVariables;
   };

struct IMPORTDBPARAMS
   {
   char* dbname;
   char* provstr;
   int nTables;
   IMPORTDBTABLEDATA* Tables;
   };

You fill the IMPORTTDBPARAMS with the name (optional) , the provider string (check ADO documentation for details), the number of tables you wish to import, and then you fill an IMPORTDBTABLEDATA structure for each of these tables - containing the table name, the XMLElement* item name to store, the number of variables to take (columns from the table) , and a double pointer to the variable names and the variable names to be stored. For an example, see xmltest.cpp.

Database Queries

You can use XMLElement :: XMLQuery() which accepts an expression to test, the deep to search (-1 if all the child elements are to be queried), and a pointer to the returned XMLElement*s (which are not duplicated; the function just copies their pointers to your array). An example below:

XMLElement* e = ... ;// get this from somewhere
int nC = e->GetAllChildrenNum();
XMLElement* a = new XMLElement*[nC];
memset(a,0,sizeof(XMLElement*)*nC);
int nR = e->XMLQuery("some_var == \"*5*\"",a,-1);

for(int i = 0 ; i < nR ; i++)
 {
 ... // use a
 }

delete[] a;

The above code returns pointers to all children elements that have a variable with the name 'some_var' which has a '5' inside (regular pattern expressions are supported). For more, see XML.CHM.

Other Features

These are some other current features:

• Use XML :: ImportDB() to import a database (every ADO database supported) to an XML element (examples are in the help file)
• Use XML :: Query() to query the database

These are some features I'd like to implement in the future:

• Case-insensitive functions
• Partial XML Load/Save
• XML Compression

Please leave your questions and comments!

Sample Projects

• XMLTest: A command line demo to discover the mains of the library
• TXML: The full database/XML file solution for Win32: Exploits all the power of the library. Features:
  • MDI XML loader
  • Load from file, URL, encrypted file (AES 256), import ADO database, load clipboard, TODO: Load Partial
  • Save to file, encrypted file, export text, export to registry key
  • Copy/Cut/Paste, Copy/Cut/Paste to Windows clipboard, Copy/Cut append, Rename, Delete
  • XML Check Integriry, XML Compress
  • View menu: Not yet implemented except 'Toggle View' F4 which toggles to:
    • Plain XML
    • Database - type XML (very useful for storing database-type items like tables). Grid-style editor
    • Plain Text
  • Insert element/variable/comment/content
  • Execute query, opening a new XML file with query results
  • Auto updates from Internet
  • CAUTION : Does NOT autosave the loaded XML file, and it closes them without checking if they are saved first. Press Ctrl+S manually to save files.
  • CAUTION : No undo. If you mess it up, I am sorry :)
• XMLPPC: The lite XML editor for Windows Mobile 5+. Supports every feature as TXML, except multiple files opening and database queries.

History

• October 20, 2008 - Update 0x143
  • Added optional namespace XMLPP
  • Converted constants of "Savemode" "Loadmode" and "Targetmode" to readable enums
  • Added extra protection to avoid crashes in case of malformed XML.
  • Replaced many 'int' s with 'size_t' allowing further expansion to X64 and eliminating C4267
    Added "Const" to more functions
• July 23, 2008 - Update 0x141
  • Added ability for comments to have < and >
  • Fixed some crashes due to malformed XML files
  • Added const to some functions
  • Added SetValueInt64 and GetValueInt64
  • Fixed SetValueInt to use %i instead of %u
  • Other minor fixes
• April 27, 2008 - Update 0x140
  • Added XML :: SetUnicode()
  • Fixed bug in element updating
  • Changed Item param to be 64-bits
  • Fixed small bug in 64-bit Z<>
  • Fixed bug in XMLElement :: MoveElement
  • Added Temporal Elements
• November 22, 2007 - Update 0x139
• Some bug fixes
• Item updating with XMLElement :: UpdateElement
• October 31, 2007 - Update 0x136 
• Added item borrowing and mirroring
• October 22, 2007 - Update 0x135 
• XML :: XML, XML :: Load() and XML :: Save() accept Unicode filenames
• October 13, 2007 - Update 0x132 
• XML is now x64 compatible
• Added XDB.CPP to demonstrate usage of XMLDialog()
• September 4 , 2007 - Update 0x12F 
• Implementation of Element Unloading/Reloading
• August 20, 2007 - Update 0x12E
• Faster saving to memory
• August 19, 2007 - Update 0x12D 
• XMLQuery bug fixed
• Badly formed XML bug fixed
• Added text-versions of XMLElement :: AddElement, AddVariable, AddComment, AddContent , AddCData
• August 7,2007 - Update 0x12B 
• CData bug fixed 
• Sequence bug fixed
• June 22, 2007 - Update 0x129 
• CData bug fixed 
• UTF-16 writing support
• June 21, 2007 - Update 0x128 
• XMLCData added
• Some minor bugs for gcc/utf-16 fixed
• CHM help file format
• June 08, 2007
• TXML.EXE for Win32 added, exploiting all the features of the library (Currently binary only, no source)
• June 01, 2007 - Update 0x125 
• Pocket PC errors fixed, XML::XMLQuery() updated
• AddBlankVariable bug fixed
• XMLPPC.EXE Pocket PC sample
• May 18, 2007 - Update 0x124 
• UTF-16 file reading
• Linux compilation fixed
• XML:: ImportDB() fix
• Other issues
• May 15, 2007 - Update 0x123
• Include formatting options in XML.CPP
• May 9, 2007 
• Original version posted

You must Sign In to use this message board.

FAQ  Noise Tolerance Very HighHighMediumLowVery Low  Search Messages    Layout Expand All MessagesThread ViewNo Javascript (slow)No Javascript Preview    Per page 102550

Msgs 1 to 25 of 401 (Total in Forum: 401) (Refresh) FirstPrevNext

what can i solve these linking errors? [modified] sweetier 0:43 18 Nov '08   I have programmed COM Server with ATL . Errors occur as added XMLms.lib to references. How can i solve this problem. error messages are as followed.. Error 4 error LNK2005: __encoded_null already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 5 error LNK2005: __decode_pointer already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 6 error LNK2005: _tolower already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 7 error LNK2005: __amsg_exit already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 8 error LNK2005: __initterm_e already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 9 error LNK2005: __unlock already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 10 error LNK2005: __lock already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 11 error LNK2005: ___CppXcptFilter already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 12 error LNK2005: ___xi_a already defined in MSVCRTD.lib(cinitexe.obj) LIBCMT.lib Error 13 error LNK2005: ___xi_z already defined in MSVCRTD.lib(cinitexe.obj) LIBCMT.lib Error 14 error LNK2005: ___xc_a already defined in MSVCRTD.lib(cinitexe.obj) LIBCMT.lib Error 15 error LNK2005: ___xc_z already defined in MSVCRTD.lib(cinitexe.obj) LIBCMT.lib Error 16 error LNK2005: "void __cdecl terminate(void)" (?terminate@@YAXXZ) already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 17 error LNK2005: _atoi already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 18 error LNK2005: __atoi64 already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib Error 19 error LNK2005: __errno already defined in MSVCRTD.lib(MSVCR90D.dll) LIBCMT.lib help me.. modified on Tuesday, November 18, 2008 6:10 AM Sign In·View Thread·PermaLink Re: what can i solve these linking errors? Michael Chourdakis 3:17 18 Nov '08   Hi there. XMLMS is a release-library. So you probably get these errors because you are mixing release-code with debug-code. Just recompile XML.CPP to provide your debug-code, and use XMLMS.LIB only for the release mode. Sign In·View Thread·PermaLink 5.00/5 (1 vote) about UTF-8 support turbocamel 21:06 17 Nov '08   The source XML was encoded with ANSI. I found that the output XML is the same encoding with source XML,how can i change the encoding to UTF-8? Using XMLTransform? Sign In·View Thread·PermaLink Re: about UTF-8 support Michael Chourdakis 3:15 18 Nov '08   Hi there. The library does not yet support ANSI encoding for reading, so it assumed that the reading was UTF-8 and saved accordingly. I suggest you load the file to a buffer, convert it to UTF-8 (With MultiByteToWideChar()), then pass it to the XML constructor. Later I will update the library so it does that automatically. Sign In·View Thread·PermaLink Re: about UTF-8 support turbocamel 15:52 18 Nov '08   Thanks,Michael I have fixed it out with the XMLTransform. In Encrypt i convert it to UTF-8 encoding. Sign In·View Thread·PermaLink Bug in FindXMLClose - crashes if file is unexpectedly truncated - easy fix pavie65 19:46 16 Nov '08   Hi Michael, This is a nice tool. I ran acrosss a small bug. FindXMLClose needs to check for (*a1 == 0)(unexpected end of file). Adding "if(!*a1) return 0;" in lines 952 and 1034 (approx.) in xml.cpp (revision date "17-10-2008") seems to fix it. Thanks! Paul Sign In·View Thread·PermaLink Re: Bug in FindXMLClose - crashes if file is unexpectedly truncated - easy fix Michael Chourdakis 5:33 17 Nov '08   Thanks for submitting, this bug, along with the SetValueX and GetValueX XMLVariable functions is now uploaded. It will take some time to upload to CP, so get it from the project's hp, http://www.turboirc.com/xml. Sign In·View Thread·PermaLink XMLVariable::SetValueDouble() ? AntiPro 5:16 15 Nov '08   Hi Michael, a nice feature that I feel is missing is a XMLVariable::SetValueDouble() function. I could do it myself with some string formatting, but it would be nice to have it in there like the XMLVariable::SetValueFloat() function. Kind regards. Sign In·View Thread·PermaLink problems of new release with VS6 compiler u-li 5:40 6 Nov '08   Hi, just got a couple of errors while compiling xml.cpp and xmltext.cpp. Errors are redefinition of "i" in for loops of the xml.cpp and in xmltext.cpp the enumerations of XML_LOAD_MODE and XML_SAVE_MODE Both very easy to cure: - use the enumerations instead of the (old) integer - put the definition of "i" in front of the block, delete it from for-stat Success, Uli Sign In·View Thread·PermaLink Re: problems of new release with VS6 compiler Michael Chourdakis 5:56 6 Nov '08   Yes xmltext.cpp is not updated, I will update it soon. Michael. Sign In·View Thread·PermaLink [Message Removed] Katekortez 10:30 25 Oct '08   Spam message removed Sign In·View Thread·PermaLink XMLVariable::GetValueInt64() AntiPro 16:27 22 Oct '08   It seems you have a function XMLVariable::SetValueInt64() but not XMLVariable::GetValueInt64(). Just the function I need at the moment . Sign In·View Thread·PermaLink Re: XMLVariable::GetValueInt64() Michael Chourdakis 21:19 22 Oct '08   There is such a function; look xml.h for it and see that you need to define something in order to be available. Sign In·View Thread·PermaLink How to get all children elements with the same element name? AntiPro 13:08 20 Oct '08   Hi Michael, how to get all children elements with the same element name? GetAllChildren() gives all elements and XMLQuery() documentation mentions searching for element name, but doesn't give a syntax example. Kind regards. Sign In·View Thread·PermaLink Re: How to get all children elements with the same element name? Michael Chourdakis 6:21 21 Oct '08   Hi there. Try XMLQuery with ? XMLQuery("? == "*namemask*",...); Sign In·View Thread·PermaLink Saving to memory buffer? AntiPro 17:19 15 Oct '08   Hi Michael, I'm trying to save an XML object to a memory buffer. How do I know how much memory to allocate for the buffer? Kind regards. Sign In·View Thread·PermaLink Re: Saving to memory buffer? Michael Chourdakis 20:38 15 Oct '08   This is a tough question to answer, but you are safe if you create a buffer with the size returned from 2*XML::MemoryUsage() , as this is usually an overestimation of the memory usage of the XML data. To cope with very small XML files, I usually create a buffer of 2*MemoryUsage() + 1000, which is enough. Later on I will provide a function that will give a safe estimation that is guaranteed to be enough. Sign In·View Thread·PermaLink SetEncoding bbrandin 22:30 30 Sep '08   Hi! May be I am wrong, but after XMLHeader* pHead = new XMLHeader(""); pHead->SetEncoding("windows-1251"); m_pXML->SetHeader(pHead); XMLElement* pRoot = new XMLElement(NULL, "tree"); m_pXML->SetRootElement(pRoot); m_pXML->Save(pszFileName); in file I see: <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <tree/> What can be done? Sign In·View Thread·PermaLink Re: SetEncoding Michael Chourdakis 0:58 1 Oct '08   Hi there. Currently the library supports only utf-8 or utf-16. It won't see anything other than that, and even if you manually set the encoding XML::SetEncoding, it will reject your recommendation while saving the data. Hopefully I will upgrade it soon to provide for more encodings. Sign In·View Thread·PermaLink Suggestion: base class [modified] bilo81 2:55 18 Sep '08   Keep up the good work! A small suggestion: why you don't create a base class for XMLElement and XMLVariable so that both of them have GetName and GetContent? It make things more "abstract" and easier to use... Since I'm just coming from .NET and C#, XMLAttribute instead of XMLVariable sounds better... I've also added this "utility function" char* XMLContent :: GetStringValue(int NoDecode) { char* value = new char[GetValue(0) + 1]; GetValue(value, NoDecode); return value; } Anyway, thank you for this great work, I really like it! Marco modified on Thursday, September 18, 2008 10:08 AM Sign In·View Thread·PermaLink Parsing Error in Attributes [modified] Paul Watt 16:28 7 Sep '08   Hello, I am looking at your XML parser and it looks like there is a lot of great work in this small source. I have run across a parsing issue with data that could appear inside of an attribute. I have some XML that has an element that looks like this down the chain: ... <relation name='Son/Daughter'> <sub_element id='101'> </relation> ... There error is in FindXMLClose, and it appears that your parser incorrectly interprets this as the closing tag to an element that is empty because single quotes ' are used instead of double quotes " to identify attributes. I added a second test on line 980 of xml.cpp to check for the single quote and it appeared to fix the issue: if (*a1 == '\"' || *a1 == '\'') Nest = !Nest; Best Regards, Paul modified on Monday, September 8, 2008 1:15 AM Sign In·View Thread·PermaLink Re: Parsing Error in Attributes Michael Chourdakis 11:39 18 Oct '08   Hmmm , can XML attributes be in single quotes ? Sign In·View Thread·PermaLink Save out formatting KenThompson 9:31 6 Sep '08   I noticed that if an element of mine contained 'content', the XML output would include additional carriage return + line feeds. I modified the source so the XML does get output like this: 1 instead: 1 Sign In·View Thread·PermaLink how can i close the file??? nere 23:45 2 Sep '08   Thanks a lot for your library, its perffect but i´m having problems when i want to remove the xml file. I think its because the file is open, my question is that doing delete xmlfile, is the file closed??? or i have to save() before delete. thanks in advance Sign In·View Thread·PermaLink Re: how can i close the file???