Denis,

I didn't understand what a property has to do with a directory. This two different things.

Lets see.
Check the properties node for a name Database, check the property SecureCustomProperties for database to.

The direct editor gives you access to the tables that store all the information. (ISE is mostly a interface to MSI database.) I should be one of the last nodes in the tree. If not check the menu for something like tools / direct editor (it should be somewhere). Sorry, I can not give you clearer advice, i have a german copy of ISD and you a english of ISE so there are some differnces. If you could not find that item you need ORCA.

Other question.
Have you create a new setup that does not much more then to copy a single file to a directory named database?

Agnes

>Hi Agnes,
>I am 100% sure the problem happen when directory has name "Database" I found this information on google , but realy don't understand how to fix it :)) The problem - ISE has keyword "Database",, and some other keywords which can't be used ..
>
>This is solution from google I found
>
>

>If you have these undocumented MSI properties listed in your Directory
>table, then MSI will generate errors. Some of the errors generated are:
>Internal Error 2318
>Fatal Error 1603
>
>Besides the properties in the Property and Directory tables, some other
>properties to avoid using in your project are listed below. (You may access
>the Directory and Property tables by going to the Direct Editor view under
>the Advanced Views option of the IDE Main Menu.)
>
>CLEANUPUNINSTALLROLLBACK
>CLIENTPROCESSID
>CLIENTUILEVEL
>CURRENTDIRECTORY
>DATABASE
>SUPPORTDIR
>ISSETUP_UISEQUENCE_PROCESSED
>ISSETUPDRIVEN
>ISSETUPFILESCOMPLETED
>ISStartupEvent
>OriginalDatabase
>PackageCode
>PackagecodeChanging
>SourcedirProduct
>VersionMsi
>

>
>But the problem.. I can't understand sentence "You may access
>the Directory and Property tables by going to the Direct Editor view under
>the Advanced Views option of the IDE Main Menu"
>
>What the Direct Editor.. where "Advanced Views" ? :(
>
>Thanks
>Denis
>
>
>>Hi Denis,
>>
>>it's hard to find failures ins Setups, not quite as comfortable as with VFP. I use ISD not ISE, so I have no idea how much ISE is crippled. But never mind its all just a database. A lot of that what you can do depends on the level you know about MSI databases. Check microsoft, there is an SDK what ships with an msi editor (ORCA) to.
>>
>>If you get an errornumber, google for those.
>>
>>is the a first time setup or an update. If an update, have you folowed the rules for major updates?
>>
>>I see several ways ways
>>- no knowlegde about MSI
>>+recreate the setup from scratch. If this is not a first setup but merly an update you need to keep all the little GUIDS (Update/Productcode, the Componetcodes) you might copy them step by step from the old setup
>>
>>-You know how MSI works.
>>+check ISE's "Direct editor" node if available on your project and check what happend with directory table. Check component table against directory.
>>+if ISE opens MSI tables check the MSI created by ISD the same way.
>>-if there is no "Direct editor" node or the ISE does not open MSI files, get yourself a copy of the SDK and use ORCA to check the tables.
>>-if you can not get ORCA, see if you acces the sdk help files at least. The MSI engine on your comp is acessible via automation, so you might open the tables from VFP. The SDK gives VB examples.
>>
>>>Hi,
>>>When directory structure has directory entry "Database" setup fail with interne error. Is there a way to save Database directory name and avoid error... or.. what to do in this case
>>>
>>>The installshield express visual foxpro edition version 3.5 SerivcePack 4.
>>>
>>>Thanks
>>>Denis