Hi Leroy,
>Is it possible to use source control with VFE?

Yes, basically -- just like any other VFPro project. With that in mind, ya gotta remember that VFP project manager (and therefore the VFExpress extention of it) is not going to be multi-user/developer accessable.

>I have a team of 2 developers and we want to use VFE.
>What should we do?

But here's a good plan that will allow for your 2 developers to work on the project simultaneously:
First, concider that in VFE, classes are built in nTier layers as Cursors, DataEnvironments, BusinessObjects, PresentationObjects and finally Presentation Forms. By default, VFE wizards will suggest that all Cursor classes be stored in a .VCX named aCursors. All DataEnvironment classes default to aDataEnvironment.VCX, BizObjs in aBizObs.VCX, etc.
Instead of storing *all* Cursors in aCursor (a horizontal approach across one tier at a time, if you will), store the "Customers" Cursors (for example) into aCustomers, followed by storing the Customers DataEnvironment into aCustomers, then Customers BizOjbs, Customer PresentationObject and Customer PresentationForms into the aCustomers.VCX. Then let this aCustomers.VCX be checked into VSS.
Now imagine another module of your project, "Inventory" for example, having all of it's classes (Cursors, DEs, BizObjs, PresObjs, PresForms) stored into an aInventory.VCX (this would be the vertical approach up/down throught the tiers). Check this aInventory.VCX into VSS too.
This arrangement will allow Developer1 to check out aCustomers.VCX and work while Developer2 may check out aInventory.VCX and work with it's classes. Assuming each developer is working specially on certain modules...

Make any sense? Hope this was helpful Leroy.

Steven-