Hello ,

Congratulations to Tim and his team for the product , fantastic . I hope he can allow or implentar components such reports ( See fastreport ) , TdbChart .

When I do the example of youtub for creating a form of data , data which are on a www server , loaded by IE it works and opens the table .

ask :

1 - But if I compile and publish at www , the page that opens reclamanado not find the dataset folder .

2 - He fails the data as the sample application desktop , when we published it does not create a connection to the same mysql database when he talked desktop ?

3 - How can create this connection being html and js files already on the www server.

4 - EWB is continued , will have more updates and components and / or the possibility of receiving external ?

5 - Is it possible to create some targeted examples to www and mysql , create videos like this http://www.youtube.com/watch?v=5GUFqrwN918 to www for those just starting ?

Error
http://www.domain.com/datasets/domain_name?method=rows

Thank you and congratulations

Tim will answer fully I expect, but I'll answer from some of the past discussion.
First, yes, it is still actively progressing, and my understanding is that version
2 will have a new component mechanism that will make third party components a lot
easier. It is possible today, but you have to do it yourself with no IDE support.

I'm not sure of your technical questions, but the key is that the EWB application
runs "entirely" in the browser. If you want to access data, then you have to be fed
the data from a server on the internet. That server is typically the same server
the EWB application was loaded from, otherwise you have to do special things to
allow access. So, if you want to use the EWB data server, your web server has to be
the EWB data server. If your server is something like Apache on a LAMP server, then
you'll want to have some PHP or other code that your EWB application calls to get
the data. The data doesn't have to be EWB data of course, and could come from any
mechanism. I think that 1.03 will bring a PHP script compatible with EWB data, I'm
not sure because I used a server written using Delphi and RemObjects SDK. The key
is that the back end is flexible, but you have to provide it somehow (if you need
it at all).

/Matthew Jones/

(Matthew Jones) wrote:

Tim will answer fully I expect, but I'll answer from some of the past discussion.
First, yes, it is still actively progressing, and my understanding is that version
2 will have a new component mechanism that will make third party components a lot
easier. It is possible today, but you have to do it yourself with no IDE support.

I'm not sure of your technical questions, but the key is that the EWB application
runs "entirely" in the browser. If you want to access data, then you have to be fed
the data from a server on the internet. That server is typically the same server
the EWB application was loaded from, otherwise you have to do special things to
allow access. So, if you want to use the EWB data server, your web server has to be
the EWB data server. If your server is something like Apache on a LAMP server, then
you'll want to have some PHP or other code that your EWB application calls to get
the data. The data doesn't have to be EWB data of course, and could come from any
mechanism. I think that 1.03 will bring a PHP script compatible with EWB data, I'm
not sure because I used a server written using Delphi and RemObjects SDK. The key
is that the back end is flexible, but you have to provide it somehow (if you need
it at all).

/Matthew Jones/


********************************************

Hello Matthew ,

Thanks for the replies.
I'll read more about it, have limitations in some details, I'll see how it works and certainly will help you ask and hope for the next version with direct connection:

*********************************************
Would you like to leave a comment here:

When I discovered EWB read somewhere that the embarcadero in EWB was created because developers only know delphi delphi. You do not use delphi not know what it is to have a fantastic and stable platform that does everything and then some, a tool that entraga their applications with the client even asked.

- Yes we addicts have a powerful tool that allows us to deliver services more quickly (dragging and dropping), we must not lose the job by vanity to stay one year coding.

- Desktop Applications will not die because they give credibility and security for businesses, the amount of tools and data security are accessible even without internet in their offices.

- Delphi applications accessing databases hosted on www smoothly and falls.

I handed one application to 2000 columns and 5000 components on a single form that is distributed in tabs delphi and will be the EWB.

Usually these comments are from people who are developers users, like me, have never done anything like that, just use the tool to work.

If you do not like, we like.

Please respect the delphi and EWB and its creators.

Sorry for the rant and thanks for allowing us to work there.

regards,

Mauricio

Mauricio,

<< Congratulations to Tim and his team for the product , fantastic . I hope
he can allow or implentar components such reports ( See fastreport ) ,
TdbChart . >>

Thanks, and yes, there will be more visual components coming.

<< 1 - But if I compile and publish at www , the page that opens reclamanado
not find the dataset folder . >>

This is because the web server that you're using does not know how to serve
up JSON for EWB datasets.  The EWB Web Server includes this capability, but
only runs on Windows.  But, as Matthew indicates, the upcoming 1.03 includes
PHP scripts for serving up the dataset JSON on Apache, etc.  However, the
PHP scripts initially only work with ElevateDB though the ElevateDB PHP
Extension, and other database products such as MySQL will need to have some
PHP code added to implement the PHP classes that provide this functionality.

I've attached the 1.03 PHP scripts so that you can get an idea of how they
will work.  The ewbdataset.php code would need to be implemented in the same
way as the edbdataset.php code in order to have it work with MySQL
(mysqldataset.php).  I'll be eventually implementing it, but I don't have
any timeframe yet on it.

The cdcollector.php code shows how to define ElevateDB datasets and then
allow the common dataset manager to handle all of the dataset requests.

Note: these files are for illustration only and will ship with 1.03 and
higher, so don't rely on them to be current after 1.03 is released.  Also,
they will *not* work with 1.02 since the dataset URL handling has changed a
bit in 1.03 (breaking change) to accommodate PHP back ends.

Tim Young
Elevate Software
www.elevatesoft.com

Hello Tim,

Thank you for your attention and sorry for the delay by thanking you is that year-end is run.

Glad you made it and all the updates to come.
What I did is that:

1 - To host a project it must be in VPS?
      1.1 - We copy the server there that is loaded like a loca server?

2 - Using Json no need to VPS?
      2.1 - JSON (JavaScript)?

3 - What is the best option (VPS or JSON)?

4 - JSON This layer is responsible for connecting to the mysql database, or all transactions (Ins, Udt, Del, Select) with msql?

5 - What are the modules generated from Delphi XE?

6 - Is there a website available for viewing working with EWB?

Sorry to interrupt work.

Thanks and Merry Christmas Health.

Maurício wrote:
1 - To host a project it must be in VPS?
      1.1 - We copy the server there that is loaded like a loca server?

Not exactly. It only needs to be VPS if you wish to use the EWB web server. if you implement your own web service then you this could be a pure php/mysql implementation.

2 - Using Json no need to VPS?
      2.1 - JSON (JavaScript)?

if you wish to use EWB dataset handling capability you will always use JSON. The VPS is only needed if you use EWB web server since you need windows to run it on.


3 - What is the best option (VPS or JSON)?

You will use JSON no matter what - if you want to use EWB web server (meaning server side will work "out of the box") then use VPS.

My suggestion is to start with EWB web server and VPS so you can concentrate on your client side application (EWB application). This also gives you an opportunity to get better understanding of the web request architecture:

http://www.elevatesoft.com/manual?action=topics&id=ewb1&section=using_server_requests


4 - JSON This layer is responsible for connecting to the mysql database, or all transactions (Ins, Udt, Del, Select) with msql?


JSON is simply a data format used for encoding of data and commands EWB datasets use. You still need something on both ends of the communication to alternate and handle JSON. In this case back end web service component (like EWB Web Server) knows how to deal with the JSON and then connect and work with the back end database.

Current JSON can represent all of those request types. JSON itself does not know how to connect to MySQL but your web service does know that.

I suggest you review the EWB manual for datasets:

http://www.elevatesoft.com/manual?action=topics&id=ewb1&section=using_datasets

Raul

Hello Raul, thanks for the feedback.
could also run in the browser with ewbsrvr.

Now and hosted test and verify how the components need to be configured.

Also installed in the server, 2008 server and installed the driver ADBC 5.1 and 5.2, the two have connected without issue on the bench at www.

But in the dataset manager configuration screen -> property connection -> connectionstring option = Provider = MSDASQL.1; Persist Security Info = False; Data Source = MySQL 5.x.
Odbc connection directly by the server ok.

By web builder incompatibility and DNS issue.

At the same setup windows Xp is ok.

Have you seen this error?

Something in particular with the 2008 server?

Merry Christmas and .2000 and always very healthy.

Mauricio,

<< But in the dataset manager configuration screen -> property connection ->
connectionstring option = Provider = MSDASQL.1; Persist Security Info =
False; Data Source = MySQL 5.x.
Odbc connection directly by the server ok. >>

So, you're saying that the connection works ok in the EWB IDE's DataSet
Manager, but not with the EWB Web Server running on 2008 Server ?

Tim Young
Elevate Software
www.elevatesoft.com

Hello Tim,

happened to me as well:

1 - Testing the direct connection through ODBC in XP = OK

2 - Testing the ODBC connection in XP by ewbsrvr = Ok

3 - Testing the ODBC connection by 2088 server = Ok

4 - Testing the same configuration of the ODBC connection in ewbsrvr 2008 server = [Microsoft] [ODBC Driver Manager] The specified DNS contains a mismatch between the Driver architectures and application

I'll see if the DNS service is installed on this server that is only used to care database. Can this be?

On 12/26/2013 2:16 PM, Maurício wrote:
> 4 - Testing the same configuration of the ODBC connection in ewbsrvr 2008 server = [Microsoft] [ODBC Driver Manager] The specified DNS contains a mismatch between the Driver architectures and application
>
> I'll see if the DNS service is installed on this server that is only used to care database. Can this be?

It sounds like a case of 32bit and 64bit being mixed. Is this a 64bit
server ?

The EWB Web Server is a 32bit app at this time so you should use the
32bit "c:\windows\sysWOW64\odbcad32.exe" to manage 32bti data sources
for it.

Raul