Yup the syntax Paul used is spot on. I just though it might be worth mentioning why. The RecordSource property is not a pointer to a DAO or ADO RecordSet object as the RecordSet property in any number of VB6 controls would be. Although forms do have a Recordset object property from Access 2000 onwards.
The VBA properties tend to be strings rather than objects, at least in the properties dialogue boxes. Another example would be how it handles Font properties i.e individual properties rather a link to a dialogue box allow you to set the properties of a Font object. The forms, reports, and controls also tend to be collections of common VB controls e.g. forms have scroll bars and DataSource controls "built in".
Usually you can code in a more object orientated way in the VBA editor, but it does require more work and makes it a little less RAD. The VBA philosphy has been to make it visually less heirachical for frequently used/set properties. You've less control, but it makes it easier to get going which is fair enough considering the target audience ain't the coding community...horses for courses.