Not quite sure why it should be so slow Grigor (but you do have a lot of fields and so many memo fields!)

If the data in your select is not going to change much you could consider selecting it out into a table on your c: drive at startup time.

If this works then your 90 seconds will only happen the once at startup.

Of course then you have the problem of getting any changes to your main data back into your temporary table on the C: drive.


Hope this idea is of some help


>Hello, All.
>
>I've got a problem. Here it is:
>
>I have a database in network's file server. One of database's tables had 147 fields, with 3930 bytes total record length. About 30 of table's fields are memo type.
>
>Application have one entry form, in wich use must select one record. In this form, I have a SQL Select command like this
>
>SELECT id,firstname,lastname,dataext,dataint,cnp from pacienti into cursor crPacienti
>
>As you see, this command should download 6 fields from table into a temporary cursor. Then, I have a listbox with this cursor as rowsource.
>
>Original table have about 800 records.
>
>Select SQL command needs about 90 seconds to execute. Network is at 10 mbs one.
>
>I've have tested many variants: with a view in database, with a SQL statement as rowsource, and so on. The same result.
>
>Momentarily, I have two tables, one-to-one relationed: the big one, with 147 fields and the small one, with 6 fields. I use the small one as rowsource, and seems to be ok, but I don't like the approach.
>
>Can anybody give me an idea?
>
>Thank in advance