ACTEBS
actebs at actebs.com.au
Wed Oct 13 06:11:28 CDT 2004
Susan, You're a god. What was stuffing things up was that I was doing: Set Me.RecordSource = rst Instead of: Set Me.Recordset = rst Thanks Vlad -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Wednesday, 13 October 2004 3:25 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Recordset to a Continuous Form I'm probably missing something real obvious here, but this worked for me. I used AutoForm to create a quick form on Employees, then changed it to a Continuous form and deleted the RecordSource property. All the controls remained intact with their default Name and Control Source property settings. Then, I used the following code to populate the form: Private Sub Form_Load() Dim rst As ADODB.Recordset Set rst = New ADODB.Recordset rst.Open "Employees", CurrentProject.Connection, adOpenStatic Set Me.Recordset = rst End Sub Worked for me -- form is still continuous and it doesn't update the underlying source. It's strictly a browsing form. If you wanted to update, you could change the adOpenStatic setting. I didn't spend much time testing it either, so I may be missing something. Susan H. The problem is still one of continuous forms. The only thing that creates a continuous form is a bound recordset. With unbound forms, you have to view one record at a time. A continuous form is an optical illusion of sorts, with only one set of controls on the form, so there is no unbound equivalent unless you want to populate a list box or a grid with the data. -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com