>>>As I read Chapter 31 of the documentation, it states the VFP 5.0 only supported UI for display purposes. Although the documentation states that in-process Unattended servers should not have UI, the documentation claims that all command, feactures and functions are available to the single thread DLL. The documentation goes on to list the commands, feactures and functions that have been disabled in the multi-thread DLL. It also states that UI in an out-of-process server (.exe) can be disabled. What is this saying?
>>>
>>>I read this as, use it at your own risk.
>>
>>Are you _using_ VFP 5, or VFP 6?
>>
>>In VFP 6 UI is disabled. In VFP 5, it works, but is not recommended.
>
>I'm using VFP 6.0 Sp3.
>
>All I was looking for was a way of neatly breaking a large application down into several small files so hat upgrades and bug fixes would be easy. DLL's looked like they would be the neatest. I will just go with EXE's.

Hi Fred,

This fits in nicely with some recent discussions about n-tier design. You can still utilize DLLs in a tier separate from the UI. Often, these are the business rules applicable to the application. The advantage here is that not only can you swap around other parts of the application almost at will, but other, non-VFP, applications (such as an Excel spreadsheet, or app written in another language) can utilize them as well.