>
> Thanks,
> Mike
>
> PS: To keep from having to e-mail you, e-mail is also part of my new project and I don't really want to put out the money for Exchange Server. I've downloaded (but haven't had the chance to test) the free Mercury mail server and was just wondering what you had set up for Foxite. Thanks again.

Hi Mike,

> Something else I just realized...
>
> >All depends on what you want. Foxite uses a .DBC, mainly because it can take care of the primary key generation itself.
>
> What exactly did you mean by this? In my current apps, I call a NewID procedure manually to replace the primary key when the table is OK'd to be updated. Is there some way this can be taken care of through some .DBC rules I don't know about?

Take a look at the Default Value property for each field. There is nothing wrong with calling it manually, but I choose to let the dbc take care of it.

> >It also has some default values for example a DATE() for the post_date field.
>
> Does this mean that you're not manually replacing this field either?

Yep, see Default Value.

> Sorry to pester you with these questions. I'm really looking forward to getting this running though and I want to do it right.

No problem man.

> PS: To keep from having to e-mail you, e-mail is also part of my new project and I don't really want to put out the money for Exchange Server. I've downloaded (but haven't had the chance to test) the free Mercury mail server and was just wondering what you had set up for Foxite. Thanks again.

Yep, Exchange is too expensive. It is cheaper to subscribe to MSDN Universal. We use Mercur mail server at this time, but I'd like to upgrade the whole stuff to Win2k and Exchange 2k in the near future.

--
Eric den Doop
www.foxite.com - The Home Of The Visual FoxPro Experts