Dreamweaver Recordset not recognized

Not sure if I can be helped here as its is a very old site...

In Dreamweaver cs3 I am trying to ammend an old .asp site.

I tried to use an old version of data assist but could not get it to produce a result so I thought I would try the Dreamweaver method.

I need to create an Update a Record page.
I used Menu > Insert > Data Objects > Update Record > Record Update Form Wizard.

I create a Form, then go into the wizard and A box "Set up Instructions "
opens asking me to create a recordset.
I create a Recordset and use Test button which shows all records.
I click OK and the box Setup Instructions appears again still asking for a recordset.
The recordset code does appear in the page.
I have to cancel the Setup Instructions box to proceed.

If I then try to create the update Form the recordset the Setup Instruction Box reappears the existing recordset is not recognised.

This can be seen in the attached image and code.
I quite understand if this too old to get answered
Thanks
John

if you test the recordset, does it return a result?

if you go to the bindings panel does it show a binding group for the recordset?

sounds like a problem with the site definition settings.

if the recordset doesn't display in the bindings panel, double check the site definition settings.

Thanks for your reponse Jason
if you test the recordset, does it return a result?
Yes
if you go to the bindings panel does it show a binding group for the recordset?
Yes
I tried creating a non wizard Update via
Server behaviours > Update Record but still came up with Please create recordset
The recordset is created.
Image shows.

Any ideas welcomed!

I have created a support ticket so we can look into this issue further.

To view and edit your support ticket, please log into your support history:
supporthistory.php

If anyone else is experiencing this same issue, please append to this thread.

I must thank Jason for helping me on this problem.

Jason quickly identified my problem as being the use of reserved access words perhaps 2 or even more!
Jason carefully explained how important it is to have a method whereby reserved words cannot be used.
This is best carried out by applying tbl before the table name so a table could be called tlbproducts

If the table name is tlbproducts
The field names would perhaps be
productsID
productsName
productsDescription

As Description is a reserved word in access productsDescription would not present a problem.
I write this down as a reminder to me for the future and if it helps anyone that's great also.

Many thanks again Jason and I trust I have this all correct!

Regards
John