Re: Record set not updatable

From: John Vinson (jvinson_at_STOP_SPAM.WysardOfInfo.com)
Date: 12/27/04 

Date: Mon, 27 Dec 2004 11:41:58 -0700

On Mon, 27 Dec 2004 10:03:05 -0800, DianeD
<DianeD@discussions.microsoft.com> wrote:

>Please help me with this problem, after linking 2 tables I am no longer able
>to update the recordset in a form:
>
>Table 1: I've set up an option group that stores the value in a field named
>'Reason for Return'.
>Table 2: I have 2 columns - 'Reason for Return' and 'Description'.
>
>In my form, when I use the field 'Reason for Return' from Table 1, I get the
>correct information and am able to add new records, however when I try to
>link the 2 tables so that I can add the 'Description' field to the form, the
>recordset becomes un-updatable.
>
>What am I doing wrong? Thanks for any suggestions.

Is the "Reason for Return" the Primary Key of Table2? If not, that
would cause this problem. Also, if you have <yuck, PTOOIE!> Lookup
fields in your table, you'll have similar problems.

You may also want to consider basing the Form simply on Table1 and
using a Combo Box bound to Reason for Return, based on Table2, and
displaying the Description.

                  John W. Vinson[MVP]

Relevant Pages

  • Re: Jet 3.51 transaction success rate
    ... might cause the new record to become part of that RTS2 recordset. ... Private Sub Command66_Click ... Dim MSX As String ... parent reason has any sub reasons. ...
    (comp.databases.ms-access)
  • Re: Data Layer Merits
    ... At the moment we're taking a perfectly good and workable object (an ADO ... recordset) and needlessly reshaping it into something completely different ... for no obvious reason. ...
    (microsoft.public.sqlserver.programming)
  • Re: Scan with Object or DAO.Recordset
    ... Recordset is much more specific than Object. ... The only reason the Wizard usings Object is because Microsoft tried to introduce ADO recordsets into Access 2000, where previous versions had use DAO recordsets. ... Dim rst AS DAO.Recordset ... In summary, use the most specfic data type you can, and the narrowest scope you can. ...
    (comp.databases.ms-access)
  • Re: sequential numbering in a query
    ... The reason you're not ... getting a higher number is that you're not looping through the recordset: ... Function Generate_NumberAs Variant ... > Dim strSQL As Variant ...
    (microsoft.public.access.gettingstarted)
  • Re: making a dsn connection
    ... Is there a reason you go to dotnet and keeps the recordset and not the ... > This is my original code: ...
    (microsoft.public.dotnet.general)