I was just talking to the boys upstairs and He says...

[Gunnar Swan]

The problem with one file for a database is that the index is stored with the data in the same file.
If you have to destroy the index, you destroy the data.
One quick way to force valentina to re-index, is to destroy the index files and have it build new index files.
Index files in databases have a tendency to corrupt. 
Actually, our experience is that Valentina is more reliable than say Acces from MS. Even indices on MS SQL have corrupted.
I'd re-consider "only one". I think you'll find that over time, this might cause more maintenance problems for you.

Gunnar
Practice To Pass

8/9/04 1:37:51 PM, jda <jda at his.com> wrote:

>>You can. Just specify the Mode = 1 when creating the database. This 
>>is an optional parameter so if nothing is specified, it defaults to 
>>4 which creates the 4 separate files. I don't know which Valentina 
>>you are using but here is an example in Director:
>>    CreateDatabase(gMyDataBase, the moviePath & "databaseName.vdb", 1)
>>I would think there would be a similar way in any other Valentina application.
>>--holly
>>
>>>Why can't  we just have a single database without all the hassle
>>>of those cumbersome extra files version 2.0. they seem totally
>>>unnecessary.  I just want a database that works and is solid.
>>>One file one database.
>>>
>
>I think the original email was meant for the betas list, not this 
>one. Valentina 2.0 apps require a lot of support files...
>
>Jon
>_______________________________________________
>Valentina mailing list
>Valentina at lists.macserve.net
>http://lists.macserve.net/mailman/listinfo/valentina
>


Best Regards,
Gunnar Swan
Practice To Pass
1.888.307.2050
http://www.PracticeToPass.Com