Using query as data source....

[Jono]

Simple application - 2 tables, 1 qry and 1 form only.
The main table is tblProjects and describes each of about 100 business
projects.
Each and every Project is developed under a particular business
Goal/Strategy combination. I store Goal/Strategy codes in each record of tbl
Projects.

The other table, tblGoalsAndStrategies, is simply a reference table with
Goal/Strategy codes and their associated descriptions.

I created a qry to perform a LEFT join so that I could display the
Goal/Strategy descriptions in my Projects form.
The query works ok in QBE. However, when I try to use it as the data source
for my form I cannot edit the data on the form.

The data displays OK but appear to be locked while the properties window
tells me the fields are enabled and not locked.

No doubt I must be missing something pretty basic! Thanks for any help.

Jon

[Justin Hoffman]

"Jono" <jo*****@webone.com.au> wrote in message
news:42***********************@per-qv1-newsreader-01.iinet.net.au...

Simple application - 2 tables, 1 qry and 1 form only.
The main table is tblProjects and describes each of about 100 business
projects.
Each and every Project is developed under a particular business
Goal/Strategy combination. I store Goal/Strategy codes in each record of
tbl
Projects.

The other table, tblGoalsAndStrategies, is simply a reference table with
Goal/Strategy codes and their associated descriptions.

I created a qry to perform a LEFT join so that I could display the
Goal/Strategy descriptions in my Projects form.
The query works ok in QBE. However, when I try to use it as the data
source
for my form I cannot edit the data on the form.

The data displays OK but appear to be locked while the properties window
tells me the fields are enabled and not locked.

No doubt I must be missing something pretty basic! Thanks for any help.

Jon

From a post yesterday on a similar topic... is this the issue?
You need to have the appropriate indexes on the table. In a typical
scenario, you might have two tables:
tblOrder: OrdID, OrdNumber, OrdDate, etc
tblOrderItem: ItmID, ItmOrdID, ItmProduct, ItmQuantity, etc
So you can have many line items on one order. Both tables have primary keys
(OrdID and ItmID) and the field ItmOrdID is indexed with duplicates allowed.
As an extra (and advisable) step, you can enforce referential integrity
between the two fields.
When you create a query, you will find that the join is added automatically
and the query is updateable.

[Jono]

Justin,
Thanks for the super quick reply.
As you guessed I'd got the key/indexing wrong on the reference table
Works a treat now.
ta,
Jon
"Justin Hoffman" <[e-mail]> wrote in message
news:d5**********@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com...

From a post yesterday on a similar topic... is this the issue?
You need to have the appropriate indexes on the table. In a typical
scenario, you might have two tables:
tblOrder: OrdID, OrdNumber, OrdDate, etc
tblOrderItem: ItmID, ItmOrdID, ItmProduct, ItmQuantity, etc
So you can have many line items on one order. Both tables have primary keys (OrdID and ItmID) and the field ItmOrdID is indexed with duplicates allowed. As an extra (and advisable) step, you can enforce referential integrity
between the two fields.
When you create a query, you will find that the join is added automatically and the query is updateable.