Hi,

when I forget to clear TempTablesPath of the Engine and ship my
application, the user gets an error, if the default path of my machine
does not exist on his machine.

How about changing TempTablesPath to the default Windows-Temp-Path, if
TempTablesPath is not available?

Regards Uli

Uli

>when I forget to clear TempTablesPath of the Engine and ship my
>application, the user gets an error, if the default path of my machine
>does not exist on his machine.
>
>How about changing TempTablesPath to the default Windows-Temp-Path, if
>TempTablesPath is not available?

I can understand why you say that but its a bad idea in my opinion.

Roy Lambert

Roy,

> I can understand why you say that but its a bad idea in my opinion.

Why?

If the TempTablesPath is not available, it doesn't make sense to stop
the whole application instead of using the default path.

Uli

Uli

>If the TempTablesPath is not available, it doesn't make sense to stop
>the whole application instead of using the default path.

Would you guarantee that you've remembered to change the other paths? If I've forgotten something like that I want to know. You may have had good reasons for setting the path as you had, but forgot to have the directory created by the app (or user if you trust them). Would you still want the engine to decide it knows best?

Roy Lambert

Uli,

<< How about changing TempTablesPath to the default Windows-Temp-Path, if
TempTablesPath is not available? >>

There's really no point in having a property for this, in that case.  You
should always assign a temporary tables path in your startup configuration.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> There's really no point in having a property for this, in that case.  
> You should always assign a temporary tables path in your startup
> configuration.

OK, accepted.

Uli