<lylefair@yahoo.ca> wrote in message
news:1116436286.600608.3610@g14g2000cwa.googlegrou ps.com...[color=blue]
> Justin Hoffman wrote:[color=green]
>> "timster" <tim.allard@sd-partners.com> wrote in message
>> news:1116410786.321672.152430@g47g2000cwa.googlegr oups.com...[color=darkred]
>> > >From Microsoft Office 2000/Visual Basic Programmer's Guide
>> >
>> > Choosing ADO or DAO for Working with Access Databases
>> > -------------------------------------------------------------------
>> >
>> > "When you use the Recordset property to set the Recordset object of[/color][/color]
> a[color=green][color=darkred]
>> > Form object to a Recordset object you created, if you set the Form
>> > object to an ADO Recordset object, the data will be read-only. If[/color][/color]
> you[color=green][color=darkred]
>> > want the data to be writable, you must set the Form object to a DAO
>> > Recordset object."
>> >
>> > Can anybody translate this into english please?
>> >
>> >[/color][/color]
>
http://msdn.microsoft.com/library/de...sdatabases.asp[color=green]
>>
>>
>>
>> I would have guessed that if you don't understand it then it means[/color]
> you don't[color=green]
>> need to. The only time this might affect you is if you write VBA[/color]
> code for[color=green]
>> your forms and programmatically create a recordset which you assign[/color]
> to a[color=green]
>> form - a technique which is probably not as common as setting the
>> recordsource property.
>> Anyway, there are two different object libraries for working with[/color]
> data - DAO[color=green]
>> and ADO and both of these libraries contain a recordset object. In[/color]
> other[color=green]
>> words you could create two different types of recordsets: a[/color]
> DAO.Recordset or[color=green]
>> a ADO.Recordset. For a wide range of tasks, either type would do,[/color]
> but not[color=green]
>> if you want it to be used as the recordset of an updateable form. In[/color]
> this[color=green]
>> particular case, you have to use a DAO.Recordset since the[/color]
> ADO.Recordset[color=green]
>> won't let you edit the data - a pretty serious disadvantage for ADO
>> recordsets.[/color]
>
>
> It would be except for one small thing:
>
> It's not true.
>
> ADO recordsets as form recordsets are editable in Access 2000. I know
> this because I have done it.
>
> And the myth that transactions cannot work with these is just that, a
> myth. I know this because I have used them.
>
> And yes, I have posted the code here in CDMA previously.
>
> One of the first things one should learn about MS is that much of its
> documentation is flawed.[/color]
Perhaps I should be more adventurous and check out some of these
undocumented features ... firstly this one, then I'll try overclocking my
processor to 3.8GHz adding extra cooling with a combination of vacuum
cleaner and fish tank spare parts.
