I think actually the best option is to use ADO (ActiveX Data Objects) directly on the client PC, assuming suitable ODBC drivers are available (which I can certainly make happen). Here's some simple sample code (obviously without much error handling):

OLEObject conn, rs
int li_return

conn = Create OLEObject
li_return = conn.ConnectToNewObject("ADODB.Connection")
if li_return <> 0 Then
    MessageBox("Test", "Cannot connect to ADODB.Connection object")
end if
// in the following, you can precede it by "Provider=MSDASQL;" but that is the default
conn.ConnectionString = "Driver=MySQL ODBC 5.3 Unicode Driver;Database=...;Port=3306;" + &
        "Server=localhost;Uid=...;Pwd=...;"
conn.Open()
rs = Create OLEObject
li_return = rs.ConnectToNewObject("ADODB.Recordset")
if li_return <> 0 Then
     MessageBox("Test", "Cannot connect to ADODB.Recordset object")
end if
// Sample select using one of our actual tables in our application (will only return 1 row, but code below handles many rows)
rs.Open("SELECT organization_name, organization_name2 from constants", conn)
do while not rs.EOF
    MessageBox("Test", rs.Fields(0).Name + ": " + rs.Fields(0).Value + "~n" + &
                         rs.Fields(1).Name + ": " + rs.Fields(1).Value)
    rs.MoveNext()
loop
rs.Close()
DESTROY rs
conn.Close()
DESTROY conn

Hi Dan;

   Yes as Mike well stated, this would be a great feature for Appeon Web. Appeon Mobile has this capability today. I agree, this would be a "kool" enhancement.

In the mean-time (besides just a bare bones FileRead ) .... my workaround suggestion would be to use another PB App EXE, as follows:

1) Appeon Web Apps can use the Run() command to execute local Apps.

2) Build a native PB App that interfaces with the local DBMS

3) Install the Local DB PB App on your Web client PC's. Note that Appeon Web has FIle Up/Down load functionality. So you could have the Web App download the native PB App EXE to the client's PC or you could save the local PB App's EXE + DLL's in the DBMS and the use a SelectBLOB command to download & install the local PB App on demand.

4) Call the local PB App from the Appeon Web App. While you can use the RUN() command - have a look at Roland's "Run & Wait" example on the TopWiz website or checkout my Run & Wait" in the STD Integrated Framework. Either way, these implementations would allow you to pass back return codes to the Appeon Web App for each call. You'll have to design the token passing scheme between the Web App and the Local PB App - but, that should be relatively stright forward IMHO.

5) Finally, you could now pass in or get back ANSI result set data streams and/or files that the Appeon Web App could process via the local PB App - which in turn, is brokering the local DBMS access for you.

Food for thought

Regards ... Chris

You could write a Windows Service app in PowerBuilder that monitors a folder on the web server for files. They could upload the database file to the web server and the service would notice that and process their data inserting it into the database used by the Appeon Web application. It would then delete the file or move it to an archive folder.

http://www.topwizprogramming.com/pbniserv.html

Local database access is not supported.   It would be pretty cool if it was, but it isn't.

you can use fileread (for flat/delimited files) as well as dll/com to process things locally.  You can have appeon server download dll/com objects that you need to use.

The final option would be to import the files to your server, then have a process on the server to handle the migration.  This could be a pure PB application (maybe kick it off via command line args), or  PB based .net / web service - but those will both require you to use a windows based server.  Or you could rewrite the server side import processing in something like python.