newDOM has no properties - At line 328 of file"WA_ProcessingObject.js" (in of course Floaters:WA_ProgressV2)

While executing timer in WA_SiteTools_ProgressV2.htm

Got trouble right here in River City. Have searched the forums with the text elements in the "Question topic" above, extensively - nothing that goes to the problem. I do have the Deprecated db tools installed (have had for some while). Have a db connection; test it periodically. Tried trashing the .dat file in Config after closing DW, then re-starting DW. No joy. Same error, as seen in the attachment.

When previously, succeeded at creating pages. Now, it stalls about 80 percent through, refuses to finish creating the page. Perhaps notably, this problem occurs as I am trying to modify, slightly, an Insert page already setup. Which went swimmingly to set up initially.

Also, should add: When setting up the page initially, got an error message. But page came together nonetheless.

Error: WADA_insert_ is an invalid variable name. As seen in (first, apparently) attachment.

Do we know, incidentally, whether there are earlier and later versions of the Deprecated tools? I notice that mine is listed as v1.0.0 in Extensions Manager. And it was installed some time ago. But my version of the .zxp in DisabledFeatures is dated Dec 20 2013, pretty clearly after I installed. But I can find nothing about versions, in a google search. Do we know whether it matters to uninstall / reinstall with the later dated file? and whether it is safe to do so? and will actually do anything useful? (!)

[UPDATE on the immediately above: Just have word from the Adobe forums

http://forums.adobe.com/thread/1433019

that apparently there is only the one - 1.0.0 - version of the Deprecated tools.]


Mac 10.8.5 DW 13.2 Build 6466 (latest I can pull out of CC) Data Bridge 1.1.8

Appreciate resolution. In (serious) trouble, until can move ahead.

Thanks as always, David

Please provide a Skype username or a US phone number and a good time to contact you when you will be in front of your computer and we will have an engineer contact you to resolve this issue over the phone.

We are available Monday - Friday from 9am - 4pm EST (except major U.S. holidays).

Thanks, Jason.

Please see PM

Jason, I'm here. Working away, so no lost time. Just being sure it's known I am in place, post 1 PM / 10 AM, and with Skype launched. (Does the Skype handle need to be 'in the clear,' out of the PM? If so, let me know of course.)

see PM

Jason, I am just everlastingly grateful … it worked! You nailed it on all accounts.

I edited the db to eliminate mySQL reserved words from table names, et al. I had failed to set the character encoding in the Dynamic Connections dialog - after correcting that, results from the db now show full utf8 in the browser. For good measure, I again trashed the .dat file.

Especially, I now do not overwrite files when 'creating' with DataAssist. Instead, I always trash any prior file. When a tweak is indicated, I invoke a preset to preserve and call up prior work. For the file path, I keyboard it in.

It all worked, flawlessly.

My great appreciation. This is truly fine service, informed in the fullest depth.

Onward. Thanks! David

my pleasure, glad to hear it is all working.

I seem to be having the same issue. Should I start a new thread or can you help me here?
Many thanks,
Simon

in david_allen's case, the problem was being caused by the table being used.

The table being used did not have a primary key column defined, and some of the columns used reserved words for their names.

when you get this error, are you using one of the application presets? or are you using the new from blank preset option?

are you using your own table? or having the wizard create the table for you?

if you are using your own table, please provide an SQL dumop that shows the table structure.

make sure that a primary key is properly defined in the table and that you are not using any reserved words for the column names. see this page for a listing of reserved words:
https://dev.mysql.com/doc/refman/5.7/en/reserved-words.html

to prevent the possibility of reserved words, the naming convention i like to use is to have the table names as part of the column name, for example:
table: products
productID
productName
productDate
etc...

or:
table: users
userID
userEmail
userPassword
userRegistrationDate

It's a really simple table created by myself. I'd set a primary key and can't see any reserved words. SQL dump with a couple of test entries is attached. Was just using Data Bridge to quickly set up the admin side.
Simon