| Subject |
Re: Remote access to a dBase database living on a private server from |
| From |
Mervyn Bick <invalid@invalid.invalid> |
| Date |
Wed, 9 Dec 2020 08:36:38 +0200 |
| Newsgroups |
dbase.getting-started |
On 2020/12/08 17:47, Franck wrote:
> Hi there,
>
> I need to work with a dBase database that lives on a private server, from the cloud (Amazone web services). I personally know nothing really about dBase, but I need to connect an app that lives on the cloud to that dBase instance.
>
As I understand it, you simply want access to a dBASE database (i.e a
set of .dbf tables) which lives in the cloud. Some other application
placed the tables and maintains the tables. You want to be able read,
and perhaps write, to these tables.
If the the original application can read and write data to .dbf tables
in the cloud you should be able to do the same using the appropriate
ODBC driver and the same connection string. You will, however, need to
install the appropriate 32-bit ODBC driver (dBASE is 32-bit) on your
computer.
dBASE has a GUI interface but, if your programs don't need to display
data or receive input while running, the required.prg files can be
written using the sourcecode editor or any text editor for that matter.
If you have a reliable connection to the cloud there should be no need
for a local copy of the database. If necessary though the dBASE
updateSet object should be able to create local copies of the .dbf files
without a problem.
With the correct connection string you should have no problems
connecting to the database. (We should be looking at minutes for this.)
And if the ODBC driver connects successfully you should have no
trouble connecting with dBASE using the ADOdatabase and ADOquery objects.
As an ODBC connection normally uses SQL as the query language you
should, in fact, be able to access the data using other languages.
(Nothing is impossible if you don't have to do it yourself. :-) )
> So.... anyone has some idea of whether or not I'm about to dive into an bottomless rabit hole trying to do that? Is rebuilding the dBase part into the wider application a better idea than trying to salvage it with tricky connections?
>
If you have access to the .dbf files you only really need consider
moving to a backend server if table size and speed of access are
factors. On the other hand there are definite advantages to using a
backend server instead of .dbf tables. Changing an existing
application to access a backend server is, however, not something to be
taken lightly.
Mervyn.
|
|