Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Force read of a dbf
Message
De
29/01/2016 03:25:56
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Allemagne
 
 
À
29/01/2016 03:12:17
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 8.1
Network:
SAMBA Server
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01630339
Message ID:
01630405
Vues:
45
TS Terminal Server?

Any interactive stuff is on CA and I can wrap it. No problem here, all under my control.
The problems are imports that where previously exclusive and for that directly on the table.
So customer does that now on hourly base, it's a bit hard to close the whole DBC everytime.

The import, by it's nature, does some bulk stuff over a couple of tables. But not for any record in those tables, the others must remain changeable. I think the locking of the interactive logic is not a problem, I can manage this pretty well through inheritance.

The problem is if I run into a locking and wait until it is finished, I have problems to recieve the finished state. This is, a single flag is switched to "unlocked" and for some reasons the TABLEUPDATE does not read this change. It's only a problem if

on source the flag is unset
CA is filled
on source the flag is set
CA sets the flag
CA TABLEUPDATE
-this fails due to changed flag in source, what is fine
on source the flag is reset
CA is TABLEUPDATE again (record on CA is not changed, still modified)
-now it should work but it doesn't





>Lutz,
>
>I cannot get a clear visualization from the description (and am in a bit of hurry...)
>You have to think of the (bulk) update you want to make and the possible update strategies done from other computers/programs as a whole.
>A lot depends on how other applications will handle their updates - writing out only changed fields or whole records and what checks are done to the record before that. There is a lot of reason behind forcing everybody out, bulk updating and allowing normal use to resume.If that can't be done, you often have to create stage tables and do single updates flowing with the update pattern used in the other applications. If you have different update patterns in those applications, get the process rolling to streamline into one pattern.
>One of the nagging doubts from your description is that other apps might happen to overwrite your in-between changes - is everything working with CA and wgich fields are updated ? Do you have a TS-based logic in place ?
>
>HTH
>
>thomas
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform