PDA

View Full Version : stuck with the most simple example (Ajax Form -> "unkown-table-error")



news.dataaccess.com
22-Sep-2007, 07:09 AM
Hi everybody
Inspired by the seminar yesterday in lucerne I tried to create a small
AJAX-application based upon the "AJAX Library Quick Start.pdf" which comes
with the Library (in the Help-Directory).
Well ... I did (almost) everything as in the PDF but somehow it didn't work.
Instead of using the example-databases I've created my own one.
also Called Customer with the following fields:
Customer_Nr
Name
Adresse

There's also a System-DB for autoincrementing the Customer-Nr.

Everything worked ... the default-Page looks well and exactly as in the
Quick Start-pdf...
But when I open the Customer.asp I get these two Ajax-Alerts:
Unkown Table: customer (form: customer_form field: customer__customer_nr)

Error 210 occured: Status 405 accessing undefined

Does anybody have an idea what i've missed or made wrong?
I guess it's something easy that I've just overlooked ...

kind regards,
Raphael Theiler

Raphael Theiler
22-Sep-2007, 12:30 PM
Allright...
Got some news ;)
First: in the ASP-Tempate the WebService was a WebService.wso which i
changed to WebService.wo because the Studio created a wo-file and not a wso
;) The WebApp-Server didn't associate the wo-file-extension ... only the wso
.... so it didn't work at all ;)
Anyway ... after registering the wo-fileextension too I get an other Error:

Error 210 occured: Status 404 accessing undefined

Well... in my Reference-File I couldn't find anymore informations about
these errors.... can anyone help?

"news.dataaccess.com" <peanut_removethisnospam_@bluewin.ch> schrieb im
Newsbeitrag news:uyL2iFR$HHA.2312@dacmail.dataaccess.com...
> Hi everybody
> Inspired by the seminar yesterday in lucerne I tried to create a small
> AJAX-application based upon the "AJAX Library Quick Start.pdf" which comes
> with the Library (in the Help-Directory).
> Well ... I did (almost) everything as in the PDF but somehow it didn't
> work.
> Instead of using the example-databases I've created my own one.
> also Called Customer with the following fields:
> Customer_Nr
> Name
> Adresse
>
> There's also a System-DB for autoincrementing the Customer-Nr.
>
> Everything worked ... the default-Page looks well and exactly as in the
> Quick Start-pdf...
> But when I open the Customer.asp I get these two Ajax-Alerts:
> Unkown Table: customer (form: customer_form field: customer__customer_nr)
>
> Error 210 occured: Status 405 accessing undefined
>
> Does anybody have an idea what i've missed or made wrong?
> I guess it's something easy that I've just overlooked ...
>
> kind regards,
> Raphael Theiler
>

Raphael Theiler
22-Sep-2007, 12:52 PM
Okay .... solved it completely ;)
If you just change webservice.wso to webservice.wo in the asp-file things
won't work...
But if you copy the whole file and rename the copy to webservice.wso it
works ?!?

What am I doing wrong?

Creating a file called webservice.wso didn't work ...

"Raphael Theiler" <peanut_removethisnospam_@bluewin.ch> schrieb im
Newsbeitrag news:v3D7W5T$HHA.752@dacmail.dataaccess.com...
> Allright...
> Got some news ;)
> First: in the ASP-Tempate the WebService was a WebService.wso which i
> changed to WebService.wo because the Studio created a wo-file and not a
> wso ;) The WebApp-Server didn't associate the wo-file-extension ... only
> the wso ... so it didn't work at all ;)
> Anyway ... after registering the wo-fileextension too I get an other
> Error:
>
> Error 210 occured: Status 404 accessing undefined
>
> Well... in my Reference-File I couldn't find anymore informations about
> these errors.... can anyone help?
>
> "news.dataaccess.com" <peanut_removethisnospam_@bluewin.ch> schrieb im
> Newsbeitrag news:uyL2iFR$HHA.2312@dacmail.dataaccess.com...
>> Hi everybody
>> Inspired by the seminar yesterday in lucerne I tried to create a small
>> AJAX-application based upon the "AJAX Library Quick Start.pdf" which
>> comes with the Library (in the Help-Directory).
>> Well ... I did (almost) everything as in the PDF but somehow it didn't
>> work.
>> Instead of using the example-databases I've created my own one.
>> also Called Customer with the following fields:
>> Customer_Nr
>> Name
>> Adresse
>>
>> There's also a System-DB for autoincrementing the Customer-Nr.
>>
>> Everything worked ... the default-Page looks well and exactly as in the
>> Quick Start-pdf...
>> But when I open the Customer.asp I get these two Ajax-Alerts:
>> Unkown Table: customer (form: customer_form field: customer__customer_nr)
>>
>> Error 210 occured: Status 405 accessing undefined
>>
>> Does anybody have an idea what i've missed or made wrong?
>> I guess it's something easy that I've just overlooked ...
>>
>> kind regards,
>> Raphael Theiler
>>
>
>

Vincent Oorsprong
23-Sep-2007, 04:37 AM
Raphael,

No, no, no. (sorry);

The WO extension is for VDF source code and resides in the APPSRC folder.
The WSO is automatically created in the APPHTML directory and is -
technically - not much more than an INI file that needs to be processed. The
WSO file is like the ASP file for the webserver. The ASP file will be
processed by the IIS/WASASP endpoint interface and the WSO file will be
processed by the IIS/WASWSVC endpoint interface.

So, do not register the WO file as extension for your website. That is
confusing. Besides that the *.WO files are in a folder that is "normally"
not accessible by the webserver (and it should not be accessible too).

--
Regards,
Vincent Oorsprong
Data Access Europe B.V.
http://www.dataaccess.nl

Raphael Theiler
23-Sep-2007, 06:12 AM
Alright after renaming the webservice.wo to webservice.wso and compiling it
created a webservice.wso in the apphtml-directory which looks like an
ini-file.

Then i renamed back and everything works fine. Why wasn't the file
automaticly created? Was there a mistake or is this normal?



"Vincent Oorsprong" <vincent.oorsprong@reply.at.newsgroup.nl> schrieb im
Newsbeitrag news:CHFBqVc$HHA.752@dacmail.dataaccess.com...
> Raphael,
>
> No, no, no. (sorry);
>
> The WO extension is for VDF source code and resides in the APPSRC folder.
> The WSO is automatically created in the APPHTML directory and is -
> technically - not much more than an INI file that needs to be processed.
> The WSO file is like the ASP file for the webserver. The ASP file will be
> processed by the IIS/WASASP endpoint interface and the WSO file will be
> processed by the IIS/WASWSVC endpoint interface.
>
> So, do not register the WO file as extension for your website. That is
> confusing. Besides that the *.WO files are in a folder that is "normally"
> not accessible by the webserver (and it should not be accessible too).
>
> --
> Regards,
> Vincent Oorsprong
> Data Access Europe B.V.
> http://www.dataaccess.nl
>
>
>

Vincent Oorsprong
23-Sep-2007, 07:34 AM
Raphael,

The WSO file should be created automatically by the Studio.
The WO file is DataFlex source code and you may use any file extension for
DataFlex source code although it quite common to use the WO (pre 9.1 it was
named WBO) as file extension. If you use other extensions you have to inform
the Studio about the different fileextensions being DataFlex source code.

--
Regards,
Vincent Oorsprong
Data Access Europe B.V.
http://www.dataaccess.nl

Raphael Theiler
23-Sep-2007, 12:22 PM
i'm working with VDF Studio 12.0 ... it SHOULD be created .... I've no idea why it's not ;)

I try again when VDF 12.1 got released (and maybe the AJAX-Library 1.1 ;))

Grids and Child-Grid-Support and things like this would be great. And since there are some posts that promise such functions for the nex Ajax-library-release I think it's worth waiting...



On Sun, 23 Sep 2007 14:34:42 +0200
"Vincent Oorsprong" <vincent.oorsprong@reply.at.newsgroup.nl> wrote:

> Raphael,
>
> The WSO file should be created automatically by the Studio.
> The WO file is DataFlex source code and you may use any file extension for
> DataFlex source code although it quite common to use the WO (pre 9.1 it was
> named WBO) as file extension. If you use other extensions you have to inform
> the Studio about the different fileextensions being DataFlex source code.
>
> --
> Regards,
> Vincent Oorsprong
> Data Access Europe B.V.
> http://www.dataaccess.nl
>
>


--
Raphael Theiler <raphael_nospam_@black-rat.no-ip.com>

Harm Wibier
24-Sep-2007, 02:33 AM
Hello Raphael,

The "Error 210 occurred: Status 405 accessing undefined" error usually means
that the WSO mapping in IIS isn't correctly made. I've attached a screenshot
that displays where this mapping should be available! Note that it is
required to use a 8 character path like in the old DOS ages. This mapping
should be created automatically if you create the virtual directory using
the Visual DataFlex Webapp Administrator. The best way to create the mapping
is to copy the path from an VDF 12.0 application with a working webservice
(like the samples ;)).

If this error occurs the wso file usually is available, if it isn't it
should be created by the studio, or you have a problem in the application!
The (still not released) 1.1 version will only show the most important error
and then stop executing so other errors aren't shown.

--
Regards,


Harm Wibier
Data Access Europe B.V.
http://www.dataaccess.nl/

"news.dataaccess.com" <peanut_removethisnospam_@bluewin.ch> wrote in message
news:uyL2iFR$HHA.2312@dacmail.dataaccess.com...
> Hi everybody
> Inspired by the seminar yesterday in lucerne I tried to create a small
> AJAX-application based upon the "AJAX Library Quick Start.pdf" which comes
> with the Library (in the Help-Directory).
> Well ... I did (almost) everything as in the PDF but somehow it didn't
> work.
> Instead of using the example-databases I've created my own one.
> also Called Customer with the following fields:
> Customer_Nr
> Name
> Adresse
>
> There's also a System-DB for autoincrementing the Customer-Nr.
>
> Everything worked ... the default-Page looks well and exactly as in the
> Quick Start-pdf...
> But when I open the Customer.asp I get these two Ajax-Alerts:
> Unkown Table: customer (form: customer_form field: customer__customer_nr)
>
> Error 210 occured: Status 405 accessing undefined
>
> Does anybody have an idea what i've missed or made wrong?
> I guess it's something easy that I've just overlooked ...
>
> kind regards,
> Raphael Theiler
>
>

wila
24-Sep-2007, 04:02 AM
Harm,

Sorry to jump in, but the water seems to be quite fine here... :)

Off topic, this is something i have wondered about before. DAW
recommends us to use short pathnames, however Microsoft has teached
administrators years ago - since NT4 - that disabling short path names
enhances the security of your IIS machine quite a bit. It is part of
standard security hardening recommendations for windows web servers.

Here's a link:
http://technet.microsoft.com/en-us/library/Bb742515.aspx
from the page in question:
<quote>
Disabling 8.3 File Format Compatibility

Administrators usually desire backward compatibility; however one form
of compatibility is not desirable. Filename compatibility for 8.3 format
is on by default; it should be turned off so that the server does not
have to account for both types of filenames.

To restrict disable 8.3 compatibility, edit the following registry key.
HKLM\SYSTEM\CurrentControlSet\Control\FileSystem

Value name

NtfsDisable8dot3NameCreation
Value type

REG_DWORD
Value data

Default is 0
change to 1
</quote>

Imho, it would be better to:
- 1. NOT use the suggested default location of where to install VDF on a
machine that hosts web sites. Use paths without spaces instead, even
after all the years we left DOS, some MS core parts still don't like
this (sorry about the MS bashing <g>)
- 2. Disable 8.3 names
- 3. Then use the above location instead and you should be fine.

The "All" parameter kinda makes me nervous a bit as well... shouldn't
this be made more specific? (I don't expect issues here btw)

Disclaimer:
Of course as long as you're not hosting to the internet, please save
yourself the trouble and do what Harm recommends.

--
Wil

Harm Wibier wrote:
> Hello Raphael,
>
> The "Error 210 occurred: Status 405 accessing undefined" error usually means
> that the WSO mapping in IIS isn't correctly made. I've attached a screenshot
> that displays where this mapping should be available! Note that it is
> required to use a 8 character path like in the old DOS ages. This mapping
> should be created automatically if you create the virtual directory using
> the Visual DataFlex Webapp Administrator. The best way to create the mapping
> is to copy the path from an VDF 12.0 application with a working webservice
> (like the samples ;)).
>
> If this error occurs the wso file usually is available, if it isn't it
> should be created by the studio, or you have a problem in the application!
> The (still not released) 1.1 version will only show the most important error
> and then stop executing so other errors aren't shown.
>
>