Tim Young [Elevate Software] wrote:

Riaz,

Thanks.  I forgot one thing, though:  I need your DBISAM table also.

Tim Young
Elevate Software
www.elevatesoft.com


Thanks Tim,
zip file attached

butts dbisam database

Thanks Tim,
zip file attached

Riaz,

Your project works fine here with 2.04 using a local same-origin dataset, so the commit issue is probably still related to the CORS bug.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim,

will wait for the update 2.05

Thank you,
Riaz



Tim Young [Elevate Software] wrote:

Riaz,

Your project works fine here with 2.04 using a local same-origin dataset, so the commit issue is probably still related to the CORS bug.

Tim Young
Elevate Software
www.elevatesoft.com

hi again Riaz

I recently deployed a 'webapp' from a development server to a deployment server.. and.. lo and behold.. same error.. data loads fine, but unable to post. just like your original report (I think).

This is what I found.. the 'PrivateDir' on the deployment server had to be adjusted to a valid path. If you copied the settings from one machine to another, they might not be valid. Sometimes it will be valid 'by default'. But in my case, it was not. Once I changed that path to a valid 'temp' location, then all worked fine.

Anyway, thought you might want to check on that. Those settings are in the 'ewbsrvr.ini' file, or you can access them through the server config.. 'datasets -> edit -> connection properties -> privateDir'. This would have to be checked for every dataset.

regards.. Bruno



Riaz wrote:

Thanks Tim,

will wait for the update 2.05

Thank you,
Riaz



Tim Young [Elevate Software] wrote:

Riaz,

Your project works fine here with 2.04 using a local same-origin dataset, so the commit issue is probably still related to the CORS bug.

Tim Young
Elevate Software
www.elevatesoft.com

Hi Bruno,

tried that, still the same CORS error

Thanks, will await next version for the fix as Tim mentioned

Riaz



Bruno Larochelle @ Environment Canada wrote:

hi again Riaz

I recently deployed a 'webapp' from a development server to a deployment server.. and.. lo and behold.. same error.. data loads fine, but unable to post. just like your original report (I think).

This is what I found.. the 'PrivateDir' on the deployment server had to be adjusted to a valid path. If you copied the settings from one machine to another, they might not be valid. Sometimes it will be valid 'by default'. But in my case, it was not. Once I changed that path to a valid 'temp' location, then all worked fine.

Anyway, thought you might want to check on that. Those settings are in the 'ewbsrvr.ini' file, or you can access them through the server config.. 'datasets -> edit -> connection properties -> privateDir'. This would have to be checked for every dataset.

regards.. Bruno



Riaz wrote:

Thanks Tim,

will wait for the update 2.05

Thank you,
Riaz



Tim Young [Elevate Software] wrote:

Riaz,

Your project works fine here with 2.04 using a local same-origin dataset, so the commit issue is probably still related to the CORS bug.

Tim Young
Elevate Software
www.elevatesoft.com