Hi all!

I have a 4D database to witch I connect with a asp.net page via ODBC. This
is extreamly slow and 4D:s ODBC driver is not so stable.

Is there a simple way to "run" a sql server together with this 4D database,
with exactly the same data in the selected tables?

Let´s say I want to get persons from a person table joined with address,
postal code. Do this with the 4D ODBC is almost impossible. It takes to
loong time, if it works at all.
If I could run ms sql server and 4D server together where ms sql just
contains the requested tables the problem would be solved.

The reason to this idea is that we shall move from 4D to ms sql.

Any thoughts, ideas or what ever is welcome

/Marre

Hi!

I'm in almost the same (unfortunate) situation.
The ODBC driver for 4D server has a lot of problems and bugs, and indeed
the speed can be very slow if there is a large number of records.
As far as I van see, 4D Inc (ACI) has stopped the development at the
ODBC Driver for 4D Server.

Among the most annoying problems of the ODBC driver for 4D Server are:
transaction support not working, the sub-tables and BLOB/Picture fields
can't be accessed, the tables with more that 255 fields can't be
accessed (this list don't include the limitations of 4D Server itself: a
table can't have a primary key, a table can have multiple fields with
the same name, there is no true transaction support etc...).

I don't know about any automated synchronization module (or
export/import application) between 4D Server and MS SQL Server, so maybe
you'll have to implement a custom synchronization module in your 4D
database.
The most appropriate plug-in for this task seems to be 4D for ADO
plug-in ( http://www.4d.com/products/4dado.html ), that can be used to
connect to a MS SQL Server database from a 4D application.

Best regards,
Tudor Turcu
---------------------------
MA wrote:

Hi Tudor!

Thanks for youre answer. I will take a look at it and if I remember (and the
chance is not that big I will send this thread a note.

/Marre

"Tudor Turcu" <"tudor_[NO_SPAM]turcu"@email.it> wrote

Hi!

I'm in almost the same (unfortunate) situation.
The ODBC driver for 4D server has a lot of problems and bugs, and indeed
the speed can be very slow if there is a large number of records.
As far as I van see, 4D Inc (ACI) has stopped the development at the
ODBC Driver for 4D Server.

Among the most annoying problems of the ODBC driver for 4D Server are:
transaction support not working, the sub-tables and BLOB/Picture fields
can't be accessed, the tables with more that 255 fields can't be
accessed (this list don't include the limitations of 4D Server itself: a
table can't have a primary key, a table can have multiple fields with
the same name, there is no true transaction support etc...).

I don't know about any automated synchronization module (or
export/import application) between 4D Server and MS SQL Server, so maybe
you'll have to implement a custom synchronization module in your 4D
database.
The most appropriate plug-in for this task seems to be 4D for ADO
plug-in ( http://www.4d.com/products/4dado.html ), that can be used to
connect to a MS SQL Server database from a 4D application.

Best regards,
Tudor Turcu
---------------------------
MA wrote:

Hi Tudor!

I can´t find a solution to this
I have optimized my page, so it´s not that bad anymore and when the page
loads the first time, i read the data to a dataset. Then I use session to
transport it between postbacks.

It works for the moment.

/Marre

"Tudor Turcu" <"tudor_[NO_SPAM]turcu"@email.it> wrote

Hi!

I'm in almost the same (unfortunate) situation.
The ODBC driver for 4D server has a lot of problems and bugs, and indeed
the speed can be very slow if there is a large number of records.
As far as I van see, 4D Inc (ACI) has stopped the development at the
ODBC Driver for 4D Server.

Among the most annoying problems of the ODBC driver for 4D Server are:
transaction support not working, the sub-tables and BLOB/Picture fields
can't be accessed, the tables with more that 255 fields can't be
accessed (this list don't include the limitations of 4D Server itself: a
table can't have a primary key, a table can have multiple fields with
the same name, there is no true transaction support etc...).

I don't know about any automated synchronization module (or
export/import application) between 4D Server and MS SQL Server, so maybe
you'll have to implement a custom synchronization module in your 4D
database.
The most appropriate plug-in for this task seems to be 4D for ADO
plug-in ( http://www.4d.com/products/4dado.html ), that can be used to
connect to a MS SQL Server database from a 4D application.

Best regards,
Tudor Turcu
---------------------------
MA wrote: