Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Parameterized View Not Working Under Network?
Message
 
À
30/08/1997 08:54:33
Shihchau Tai
Apic Systems Pte Ltd
Singapore, Singapour
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Divers
Thread ID:
00047718
Message ID:
00047884
Vues:
24
>>>I have a parameterized view which behaves inconsistently under network environment. My parameterized view is created with 3 parameters, begin_date, end_date and stock_code. Everyone of them has got data in it. The file size is about 1.5 Mbytes.
>>>
>>>While querying in standalone PC, it works perfectly fine. However when it is brought to network environment (Novell Netware 4.1, my program is loaded on network drive), it gives inconsistent result. Sometimes, the result shows blank. Sometimes, the result shows the previous query.
>>>
>>>Any idea what is wrong? Thx in advance.
>>
>>Are you sure that you have sent a TableUpdate() to save your existing data before running the view? Views (and other SQL code) are run from data on the network, so changes still in your buffers are not found.
>>
>>Also, you might check the Novell write cache behavior. The updated information may still be in the network cache, not written to disk.
>>
>>>I also read somewhere that the limit of the table size / files size is 2 Mbytes. Is it true? What can I do if my file size exceeds 2 Mbytes.
>>
>>No, it's 2 GB (2,000 MB). Gives you a lot more space to work. :-)
>>
>>>Tai SC
>>
>>HTH
>>Barbara
>
>I don't think it has anything to do with data not in disk. The data is all in the table. I am not querying any newly entered data. I am just doing query with different parameters on old information. With the same parameters, the query returned different results from what I saw just two minutes before. The result is erratic. Nobody except me is running it. If I don't see the results, I won't believe it.
>
>Any other possibility?
>
>
>Tai SC

It still sounds like there's a problem with the NOVELL buffers. You might try adding a FLUSH command immediately before the SQL and see if that helps. Also (for testing purposes) try closing all the data and letting the SQL open the tables. You may be able to find certain conditions where it works and other conditions where it doesn't work (or is unstable).

HTH
Barbara
Barbara Paltiel, Paltiel Inc.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform