Share via

ACCESS data entry

Anonymous
2018-01-29T02:42:05+00:00

I have just created a new table, query and form structure for a new category of data within an existing database. There is no cross linking to multiple tables, just a straight flow through from table to form via a query. The database has this same flow through for around 8 tables providing views in 12 forms. All previous forms and queries have allowed me to enter data in any view.

I have now created a table but cannot enter data in the query or form. I have meticulously checked all settings in the Properties, including matching them to an existing Form that does allow data entry.

I have also copied another functional Form and rebuilt it to the new query to no avail. The block appears to be at the query level as I can enter data in a form built directly form the table.

Why can I no longer go through a query to make an editable form?

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

7 answers

Sort by: Most helpful
  1. ScottGem 68,830 Reputation points Volunteer Moderator
    2018-01-29T10:51:12+00:00

    I'm curious about this. First, Access does NOT generate columns in a query. Either you add a column in the grid by pulling it from a table list or you add an expression. Or did Access create the query from the simple Query wizard? I would urge you to post the SQL statement for us to see so you can prevent it from happening in the future.

    Also, if there were errors in the SQL statement, the setting I referred to were not correct.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-29T04:19:04+00:00

    Thanks d,

    Now I know where to look at the SQL view.

    I have generated hundreds of table>query>form sequences with only relationships between those three and no additional tables. I found a bunch of error fields in the query that once deleted moved the whole thing along. Not sure how they got there but feel I know what to expect next time.

    The whole problem seemed to grow out of a crash due, I think to one external pdf file not wanting to link to a particular record, despite it having happily linked to several other records. The database crashed and wiped the last 35 records but a backup brought them, all back to life. Because I had this particular table>query>form sequence created in the old database I copied them into the backup. The corrupted query came into the database. The crash happened in another form with no shared data with this one but the crash basically took the whole database down and erased or corrupted all data from that day, and managed to generate these error fields in the query that I didn't spot for awhile.

    Thanks,

    Andrew

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-29T04:10:16+00:00

    BY some miracle I have finally resolved the issue. The settings you refer to were all correct but I found a bunch of columns in the query that are the sort generated when there is an error. By deleting those I was able to enter data in the query view. I then just had to reset one parameter in the Form and I was away.

    Cant say I will be able to resolve the issue a second time but it certainly lay wiy the query and not the form.

    Thanks for your response,

    Andrew

    Was this answer helpful?

    0 comments No comments
  4. ScottGem 68,830 Reputation points Volunteer Moderator
    2018-01-29T03:28:03+00:00

    The first thing we need to see is the Recordsource of the form. The SQl for the query.,

    I assume you have checked that allow Edits is set to yes and the controls are not locked.

    Was this answer helpful?

    0 comments No comments
  5. Duane Hookom 26,825 Reputation points Volunteer Moderator
    2018-01-29T03:04:23+00:00

    Can you provide the SQL view of the query? Is the table related to any other table?

    Was this answer helpful?

    0 comments No comments