Newsgroup: it.comp.appl.access
Titolo: Access + MySQL + filtro che zippa il traffico

Ho un serverino sulla intranet con MySQL. Il front-end e' in access, 
usato da una decina di utenti da piu' sedi geografiche con collegamenti 
a 10 MBit.
Le form sono abbastanza dense di controlli con origine in una query e 
questo rallenta da matti le risposte della form alle azioni dell'utente.
Siccome l'ODBC scambia dati in formato ascii, che e' altamente 
zippabile, mi domandavo se esiste un qualche software che agisca da 
filtro "zippatore" del traffico.
Sono un sognatore? :-)
Ciao
Marco
PS: E' OT?

"Ux" <

Perchč non pensi a una configurazione Terminal Server invece che
Client-Sever a livello web?
Le prestazioni saranno immediate anche su connessioni lente...
Saluti.

 Le prestazioni saranno immediate anche su connessioni lente...
Puo' essere un'idea.
Quindi sul server devo fare 10 copie (1 per utente) dell'mdb ?
Ce la puo' fare un Pentium-4 2GHz, 1GB di RAM, disco SCSI 10000rpm ?
Inoltre il budget di questo progetto non prevede costi per licenze 
aggiuntive. La configurazione T.S. che dici richiede l'utilizzo di 
qualche software a pagamento ?
Grazie & Ciao
Marco

 qualche software a pagamento ?
Le licenze del T.Server vanno pagate, non chiedermi quali siano le
quotazioni attuali, devi informarti.
Chiaramente i vantaggi di una configurazione del genere superano di gran
lunga i costi (una tantum).
Un'applicazione lenta finisce per essere quasi inutilizzabile.
Saluti.

Ux <Non.Te....@Senno.Mi.Spammi> wrote:

Il driver mysql-odbc 3.51 prevede anche il protocollo compresso
Lo configuri dal pannello Origine dati ODBC nelle opzioni del driver
MySQL-ODBC
Non so pero' quanto sia valido. Non ho fatto test di compressione
;-)))

Ecco l'help 
The MySQL ODBC 3.51 Driver DSN setup dialog contains the following
controls:									
DSN Information:
Data Source Name	Identifies the MySQL ODBC 3.51 Driver, and enter
the name that you want to use it as a reference
Description	Description About the Data Source Name
MySQL Connection Parameters:
Host/Server Name	Enter the host name of the MySQL server, to which
you want to connect. By default it is 'local host'.
Database Name	Enter the default MySQL database name (catalog name)
to be used
User Name	Enter the user name
Pass Word	Password
Port	The TCP/IP port to use if it is not listening to the default
one, 3306
SQL Command On Connect	Optional SQL statement that will be executed
when connected to server
Driver Options, Advanced:
The options dialog helps in configuring the driver behavior based on
the requirements. This is mainly to tell driver that the client isn't
100% ODBC compliant. On Windows, one normally sets the option flag by
toggling the different options on the connection screen but one can
also set this using OPTION parameter in odbc.ini
Bit	Meaning
1	If the client wants the real width of the column.
2 	The client can't handle that MySQL returns the true value of
affected rows. If this flag is set then MySQL returns 'found rows'
instead. One must have MySQL 3.21.14 or newer to get this to work. 
4 	Make a debug log in c:\myodbc.log. This is the same as putting
MYSQL_DEBUG=d:t:O,c::\myodbc.log in `AUTOEXEC.BAT'  - – Enabled only
in debug mode
8	Don’t set any packet limit for results and parameters
16 	Don't prompt for questions even if driver would like to prompt 
32 	Enable or disable the dynamic cursor support. This is not allowed
in MyODBC. 
64	Ignore use of database name in ‘database.table.column’.
128 	Force use of ODBC manager cursors (experimental). 
256 	Disable the use of extended fetch (experimental) 
512 	Pad CHAR fields to full column length. 
1024 	SQLDescribeCol () will return fully qualified column names 
2048 	Use the compressed server/client protocol 
4096 	Tell server to ignore space after function name and before '('
(needed by PowerBuilder). This will make all function names keywords! 
8192 	Connect with named pipes to a mysqld server running on NT. 
16384 	Change LONGLONG columns to INT columns (Some applications
can't handle LONGLONG). 
32768 	Return 'user' as Table qualifier and Table owner from
SQLTables (experimental) 
65536 	Read parameters from the client and odbc groups from `my.cnf' 
131072 	Add some extra safety checks (should not bee needed but...) 
262144	Disable transactions
524288	Write all queries to `c:\myodbc.sql` (`/tmp/myodbc.sql`) –
Enabled only in debug mode
1048576	Do not cache the results locally in the driver, instead read
from server (`mysql_use_result`). This works only for forward-only
cursor types. This option is very important in dealing with large
tables when one doesn't want the driver to cache the entire result
set.
2097152	Force the use of 'Forward-only' cursor type. In case of
applications setting the default static/dynamic cursor type, and one
wants driver to use non-cache result sets, then this option will
ensure the forward-only cursor behavior.
If you want to have many options, you should add the above flags! For
example setting option to 12 (4+8) gives you debugging without package
limits! 
The default ` MYODBC.DLL' or `MYODBC3.DLL' is compiled for optimal
performance. If you want to debug MyODBC 3.51  (for example to enable
tracing), you should instead use `MYODBC3D.DLL`. To install this file,
copy `MYODBC3D.DLL' over the installed `MYODBC3.DLL` file.
Recommended Options:
Configuration	OPTION
ACCESS	3
VB	3
Large tables with too many rows	2049
Driver trace generation (Debug mode)	4
Query log generation     (Debug mode)	524288
Generate driver trace as well as query log (Debug mode)	524292
Large tables with no-cache results	3145731
Test Data Source:
You can test whether your settings are enough to connect to the MySQL
server using the button "Test Data Source". 
Online Resources:
MyODBC Home Page 	: 
http://www.mysql.com/products/myodbc
MyODBC FAQ          	:
http://www.mysql.com/products/myodbc/faq_toc.html
MyODBC Manual 	: 
http://www.mysql.com/products/myodbc/manual_toc.html
MySQL manual   	: 
http://www.mysql.com/doc/
(C) MySQL AB, 1995-2002, 
www.mysql.com