>One difference I can think of though is that some of the development tools available in the application are not available in the EXE. For example, it won't let you bring up the debugger in the EXE. It also won't let you bring up the Query designer or Form designer. So, if you ever wanted to give your users the ability to create their own ad-hoc reporting you would have to use something other than the Query designer.
>
Actually this is my current project, designing a form to emulate the form designer, allowing users to create their own pseudo scx table and then designing a form runner if you will that will read the non compiled scx table and create objects as stored on to a blank form. Ambitious?!?

Also working on a pseudo query designer. Heres the idea in case anyone else is trying to tackle this. One form has a combo box listing all the tables. Changing its value requeries a second combo box which pulls up all the fields in the table selected and triggers a third combo box which identifies the field type and requeries to allow valid comparisons (math for numerics etc). A query is then created and stored in a table field along with the table name, field name and comparison value. The next section allows you to combine queries by number ie. (1 or 2) would be a new query for query 1 or query 2. I use the () to indicate combination queries that are record independent and [] to indicate that the query must match for each record. (ie (1 or 2) would be data in table matches query 1 or query 2 and [1 or 2] means the record in the table matches query 1 or query 2. It's some complex coding but the result is an easy to use, very flexible query by example report generator for any group of tables, that stores common queries for reuse with minimal effort.

Projects to keep you awake to 3 am.