Jan Bucek wrote:
> On 12 Jun., 19:05, nonsense <nonse...@[EMAIL PROTECTED]
> wrote:
>
>>Tim Witort wrote:
>>
>>>nonsense seemed to utter
innews:64c59$466e7d08$49e5d12$947@[EMAIL PROTECTED]
>>
>>>>Does any version of VFP have lockfiling built in for
>>>>multi-user apps?
>>
>>>>I am currently trying to run VFP5.0 on a network with
>>>>XP and Vista clients and a linux file server. Each
>>>>client has its own VFP. This is intended to be an
>>>>update from multi-user foxbase running under an
>>>>older version of SCO unix.
>>
>>>>I am presently able to create database collisions
>>>>as I am set up with VFP on the client machines and
>>>>the app along with databases on the server. My VFP
>>>>5.0 do***entation doesn't address lockfiles so I am
>>>>assuming they don't exist?
>>
>>>>The business owner is totally enamored by the accounting
>>>>software he's running and refuses to change, so I'm
>>>>stuck updating from an interpreter that doesn't do
>>>>21st century dates correctly.
>>
>>>It sounds like you may be running an app in a multiuser setting
>>>that was not intended for that. VFP definitely has locking
>>>built in - down to the record level. However, if not implemented
>>>correctly, any conflicts would raise errors or not-so-user-friendly
>>>dialog boxes rather than gracefully taking care of things.
>>>People have been successfully writing and using multiuser VFP
>>>apps for about 20 years.
>
> Why do you try to run this app in VFP? Without rewriting it I do not
> see any advantage here and you will have troubles to run it as is -
> screens and re****ts above all.
Most things are working well in single user and getting even
better as I massage the apps. I had to make some minor changes
to get the screens prettied up, but they actually ran fine
under VFP out of the box. I'm distributing the apps and VFP
on client machines right now and the database on the linux
server, and I've been able to access the same field from
two clients at the same time. I'll try to force it to get
nastier yet by making a change from one client while two
are displaying the same field in order to see what happens.
> FoxPro is "default multiuser" since times of FoxPro DOS, but I have
> never read about FoxPro file-lock files. It is internal thing of
> FoxPro and you cannot affect it anyway. The thing im****tant to know is
> for example the FoxPro locking schema is not compatible with Clipper.
The version of the app I have was not clipper compatible and it
runs quite well (all things considered) under VFP. I tried running
foxpro 3.2 under a newer Unix, which might solve all my problems,
except for the fact that the termcaps don't work correctly for
the entire left hand half of the keyboard. The do***entation
covers this problem, however the published solution doesn't
work as advertised.
DOS Foxpro 3.2 run on fast CPU modern machines likes to puke
apparently because of the CPU speed.
> I have not tried to run mfoxplus in Vista, but it works in W2K/XP.
mfoxplus and family are all Y2K incompatible. I've done some
kludges to make the dates appear correctly on the invoices
however things like 30-60-90 day overdue payments on re****ts
no longer do the spread, it lumps it all together and gives
only the total because it can't deal with the post 20th century
dates correctly. That's the reason for upgrading. I can't fix
mfoxplus but I am able to do whatever is necessary in the
apps to get file locking to work correctly.
Knowing the location that the lockfiles are created would be
a nice shortcut for me. It is starting to look like I should
have VFP, the apps, and the database files all on the server
rather than distributed as I now have. That makes for a network
that's a lot busier than may be necessary once you throw 15
or so users on at the same time.
>>Thanks for your reply. The apps are multiuser (sbt accounting)
>>and have run fine that way for the better part of 2 decades
>>under foxbase and mfoxplus. (I'd love to switch them to
>>something other than sbt but they insist on sticking with
>>what they know and love.)
>>
>>Back to the drawing board on this one. I'm doing something wrong.
>>
>>Where does VFP write the lockfiles? In the directory with the
>>database? In the directory that has the app in it? In a VFP
>>directory?
>>
>>Thanks in advance for any light you can shed on this.
|
