Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Suddenly I cant make a DAP that accepts input. ERROR: READ ONLY!

Discussion in 'Information Technology' started by Frustrated DAP user., Jul 28, 2006.

  1. Frustrated DAP user.

    Frustrated DAP user.
    Expand Collapse
    Guest

    I've setup a few DAP pages that allow changing the data in my DB, and
    suddenly when I create one it only allows me to see data, not change it. VERY
    FRUSTRATING! Nobody seems to have the answer. It seems to have begun when I
    moved my default data connection file to the server that holds the DB. Since
    then I have not been able to create a DAP that allows input. I've even tried
    to create a page that directly points to my tables, thinking it was something
    wrong with my query. I've changed the "Default " back to my local one, no
    luck. My "Default" connection file simply points to the access database. The
    pages I created before this problem still work fine, but when I try to create
    another (identical) page with the same settings (query) it gives the error
    that you can not save the input to the underlying table. Anyone have this
    problem? How do you fix it? Microsoft doesn't seem to have any information
    about it on thier websites.
    HELP!
     
  2. Loading...

    Similar Threads Forum Date
    Cant believe its Chistmass Blogs Oct 17, 2015
    Opinion Violence Significantly Alters Children's DNA, Causes Premature Aging Breaking News Apr 25, 2012
    UK Archbishop of Canterbury Visits Hounslow Sikh Temple Breaking News Oct 19, 2011
    Sikhism Intoxicants and Pleasure Videos Jul 10, 2011
    India Binyat Sen's Contribution Significant in Chhattisgarh's "Mitanin" Programme Breaking News May 20, 2011

  3. Ken Snell \(MVP\)

    Ken Snell \(MVP\)
    Expand Collapse
    Guest

    Common reasons why a DAP doesn't allow editing of the data:

    You must define the Unique Recordset property for the page's section that
    has the data.

    You must have an element bound to the table's primary key field. It can be
    hidden, but it needs to be on the Data Access Page if you wish to edit data.

    You must use an updatable query for the recordset (note: Data Access Pages
    are more picky in what's updatable and what's
    not -- a query that works in a form may not work in a page).

    --

    Ken Snell
    <MS ACCESS MVP>


    "Frustrated DAP user." <Frustrated DAP user.@discussions.microsoft.com>
    wrote in message news:EEBBC737-0A65-4AA3-88A7-1D3E97392956@microsoft.com...
    > I've setup a few DAP pages that allow changing the data in my DB, and
    > suddenly when I create one it only allows me to see data, not change it.
    > VERY
    > FRUSTRATING! Nobody seems to have the answer. It seems to have begun when
    > I
    > moved my default data connection file to the server that holds the DB.
    > Since
    > then I have not been able to create a DAP that allows input. I've even
    > tried
    > to create a page that directly points to my tables, thinking it was
    > something
    > wrong with my query. I've changed the "Default " back to my local one, no
    > luck. My "Default" connection file simply points to the access database.
    > The
    > pages I created before this problem still work fine, but when I try to
    > create
    > another (identical) page with the same settings (query) it gives the error
    > that you can not save the input to the underlying table. Anyone have this
    > problem? How do you fix it? Microsoft doesn't seem to have any information
    > about it on thier websites.
    > HELP!
     
  4. Frustrated DAP user

    Frustrated DAP user
    Expand Collapse
    Guest

    Re: Suddenly I cant make a DAP that accepts input. ERROR: READ ONL

    "Ken Snell (MVP)" wrote:

    > Common reasons why a DAP doesn't allow editing of the data:
    >
    > You must define the Unique Recordset property for the page's section that
    > has the data.
    >
    > You must have an element bound to the table's primary key field. It can be
    > hidden, but it needs to be on the Data Access Page if you wish to edit data.
    >
    > You must use an updatable query for the recordset (note: Data Access Pages
    > are more picky in what's updatable and what's
    > not -- a query that works in a form may not work in a page).
    >
    > --
    >
    > Ken Snell
    > <MS ACCESS MVP>
    >
    >
    > "Frustrated DAP user." <Frustrated DAP user.@discussions.microsoft.com>
    > wrote in message news:EEBBC737-0A65-4AA3-88A7-1D3E97392956@microsoft.com...
    > > I've setup a few DAP pages that allow changing the data in my DB, and
    > > suddenly when I create one it only allows me to see data, not change it.
    > > VERY
    > > FRUSTRATING! Nobody seems to have the answer. It seems to have begun when
    > > I
    > > moved my default data connection file to the server that holds the DB.
    > > Since
    > > then I have not been able to create a DAP that allows input. I've even
    > > tried
    > > to create a page that directly points to my tables, thinking it was
    > > something
    > > wrong with my query. I've changed the "Default " back to my local one, no
    > > luck. My "Default" connection file simply points to the access database.
    > > The
    > > pages I created before this problem still work fine, but when I try to
    > > create
    > > another (identical) page with the same settings (query) it gives the error
    > > that you can not save the input to the underlying table. Anyone have this
    > > problem? How do you fix it? Microsoft doesn't seem to have any information
    > > about it on thier websites.
    > > HELP!

    >
    >
    >
     
  5. Frustrated DAP user

    Frustrated DAP user
    Expand Collapse
    Guest

    Re: Suddenly I cant make a DAP that accepts input. ERROR: READ ONL

    Thanks Ken that worked out great!
    Perhaps they should go into that subject in the help files.



    "Ken Snell (MVP)" wrote:

    > Common reasons why a DAP doesn't allow editing of the data:
    >
    > You must define the Unique Recordset property for the page's section that
    > has the data.
    >
    > You must have an element bound to the table's primary key field. It can be
    > hidden, but it needs to be on the Data Access Page if you wish to edit data.
    >
    > You must use an updatable query for the recordset (note: Data Access Pages
    > are more picky in what's updatable and what's
    > not -- a query that works in a form may not work in a page).
    >
    > --
    >
    > Ken Snell
    > <MS ACCESS MVP>
    >
    >
    > "Frustrated DAP user." <Frustrated DAP user.@discussions.microsoft.com>
    > wrote in message news:EEBBC737-0A65-4AA3-88A7-1D3E97392956@microsoft.com...
    > > I've setup a few DAP pages that allow changing the data in my DB, and
    > > suddenly when I create one it only allows me to see data, not change it.
    > > VERY
    > > FRUSTRATING! Nobody seems to have the answer. It seems to have begun when
    > > I
    > > moved my default data connection file to the server that holds the DB.
    > > Since
    > > then I have not been able to create a DAP that allows input. I've even
    > > tried
    > > to create a page that directly points to my tables, thinking it was
    > > something
    > > wrong with my query. I've changed the "Default " back to my local one, no
    > > luck. My "Default" connection file simply points to the access database.
    > > The
    > > pages I created before this problem still work fine, but when I try to
    > > create
    > > another (identical) page with the same settings (query) it gives the error
    > > that you can not save the input to the underlying table. Anyone have this
    > > problem? How do you fix it? Microsoft doesn't seem to have any information
    > > about it on thier websites.
    > > HELP!

    >
    >
    >
     

Share This Page