The problem is that LDT opens 3 or 4 Access databases in addition to the
.dwg file and the dynamic nature of these database connections causes excess
reads and writes every time you initiate a LDT function. I usually recommend
that users try not to use LDT across the T1 unless absolutely necessary. Use
Land Enabled Acad instead. If Autodesk ever goes to a true enterprise
database solution such as SQL server or Oracle to house the LDT data I
suspect this will not be such an issue.
Dale
"rich keitz" wrote in message
news:4075bbdf_1@newsprd01...
> When working on an LDD project on a remote server across a T1 line it runs
> slow. Opening and closing the file and general commands work okay. There
> is a big slow down when civil and survey functions are used. What is the
> solution?
> Rich
>
>