Investigation showed that this issue was the same as reported before with tables in the solution whose name starts with ‘temp_’
Removing these from the solution should fix the problem.
Handling of this case is fixed in release 3.5.6.
Rob
Hi Rob
You were right… I had not realised that I had a table beginning with ‘temp_’ (I didn’t build that table in my defence… )
Thank you for bearing with me insisting that this wasn’t the problem when in fact it was …
I have not yet updated the solution in question (when I tried to do it, it added the table again - even though I’d deleted it from the developer and the server…) I haven’t had time to deal with it over the past few days, but when I do, I’m certain I can take it from there…
Thank you
Bevil