New Database field not available?

I have added a new field to a database table field, in order to quickly add it to an existing form with validations,etc my plan is to edit the existing template that I created for these forms and re-create the pages then copy and paste the code into the existing (already modified) pages.

The new table field is not showing up in the wizzard, even after a restart of DW, any idea why or how to get those new table fields to become available to the DA wizzard?

if you open the Data Base panel, and expand the connection, then in the tables section expand the table, does the new column show there?

if not click the refresh button in the upper right hand corner of the database tab to refresh the table column list.

Yes, it did show up in the database tables without a refresh.

using your operating systems file manager, browse to your site folder and delete _mmServerScripts folder, then reopen DW and re test the Database connection.

Hi Jason,

Sorry for the delay, I got sidetracked working elsewhere on the site. :)

So, here is where I am at. I tried the above and it made no difference, but here is what I can see:

1. Opening the database tab I can see the new field listed in the database
   
2. Opening the wizzard and not trying to use a template that I saved I can see the new database field
   
3. If I open a previously saved template the new field does not show up in the list for me to modify or to add to the forms.

Please advise, and thanks! :)

  If I open a previously saved template the new field does not show up in the list for me to modify or to add to the forms.  

do you have the option to create the table for me selected?

If so, the table it is going to create is based on the original settings, and will, not include the new column, make sure this option is not selected.

Nope, not selected.. I am using an existing database.. same as the first time I set this up. I simply want to add a field with a dropdown menu and some validations - so it is "easier" to go this route rather than hand code it all. :)

PM sent.

In a Skype message you messaged me that you found a work around by selecting another table, then going back to the original table to get the new column listed, I logged that as a bug to have it corrected in an update.