Hi,

I am getting to a stage where I may need to enable Large file support
within one of my applications.

I was wondering - are their any drawbacks to using Large File Support
for all my applications, even if not needed? (ie, performance, etc).

I'm aware that if I use it all applications that access the data
directly must have it enabled (so there is no data corruption), and
that's fine.  (One of the reasons why I'm thinking of changing so all my
apps use it by default)...

I was just wondering if the default to FALSE is because of legacy
support (old systems), or whether it's more beneficial for others
reasons to have it disabled unless actually required?

Cheers

Adam.

Adam H. wrote:

> I was wondering - are their any drawbacks to using Large File Support
> for all my applications, even if not needed? (ie, performance, etc).

I've never noticed any problem. It is just a legacy thing really.

--

Matthew Jones

On 7/10/2015 3:35 AM, Adam H. wrote:
> I was just wondering if the default to FALSE is because of legacy
> support (old systems), or whether it's more beneficial for others
> reasons to have it disabled unless actually required?

There is no impact on having it on.

It started out as FALSE (and i think it required minimum windows version
back in the day as well - win 2k maybe but not 100% here) so changing
the default would (still) result in lot of issues.

Compatibility is the killer here. For example in our case some of our
customers (many very computer savy) use dbsys and odbc as well as db
utilities we occasionally provide.

Despite our best efforts to get them to use remote sessions only and
always the latest version we do run across somebody using old
dbsys/odbc/utility directly with file system access or sometimes they
have even used the one downloaded from elevate soft.

Defaulting this to ON would be a major PITA for us.

Raul

Thanks Matthew & Raul

Great to know there's no negative sides then (except mixing the two).

Raul - I completely agree. I think that changing v4 to 'default' to true
would be a bad move all around because of existing applications / legacy
support.

However if Tim is open to releasing DBISAM version 5 with some of the
other change requests that are springing up on the other thread, then
maybe this might be a perfect opportunity to default this to TRUE in v5
applications, whilst leaving V4 applications alone.

Cheers

Adam.