Paradox for Windows 4.5 and networking 
Author Message
 Paradox for Windows 4.5 and networking

Hi all. Recently I had to put our paradox database on a server and am
wondering how this thing works. The manual "Getting Started" says the
private and working directry should be on local machine. So I set them so.
PDOXUSER.NET file is on the server as well as data tables and forms and
other stuff. But if I was to run a form that's originally written for use
on local machine, I couldn't run it, for paradox reporting tables the form
is depending on is missing.

I know this is a real beginner question. But does this mean that, if I was
to create an application in Paradox whose data is on the server and actual
Paradox application is on local workstation, all the tables and queries
has to be on the server as well? What about reliability issues? Someone
from different department told me that Paradox isn't good with networking
stuff, like accessing same record on a table from two or more different
workstation can currupt the database... Could anybody give me some advice
or explanation?

Any respons will be appreciated!

Mahalo,

Cody



Mon, 06 Sep 1999 03:00:00 GMT
 Paradox for Windows 4.5 and networking

Quote:

> Hi all. Recently I had to put our paradox database on a server and am
> wondering how this thing works. The manual "Getting Started" says the
> private and working directry should be on local machine. So I set them so.
> PDOXUSER.NET file is on the server as well as data tables and forms and
> other stuff. But if I was to run a form that's originally written for use
> on local machine, I couldn't run it, for paradox reporting tables the form
> is depending on is missing.

> I know this is a real beginner question. But does this mean that, if I was
> to create an application in Paradox whose data is on the server and actual
> Paradox application is on local workstation, all the tables and queries
> has to be on the server as well? What about reliability issues? Someone
> from different department told me that Paradox isn't good with networking
> stuff, like accessing same record on a table from two or more different
> workstation can currupt the database... Could anybody give me some advice
> or explanation?

I've been using Paradox on a network since version 4 for DOS.  Currently running version
7 for Win95.  You may have to rewrite your application to make use of the network.  I
had to do that way back there when we first went to the network.  You should have your
application and all data files on the server.  The answer tables generated by queries
will be put in your private directory.  I also have some empty, temporary tables sitting
in my private directory to hold results of a series of queries.  Report formats and
forms are on the server.  Reports can pull their data from either the server (working
directory) or from the private directory.  This is very helpful in case two people try
to run the same report at the same time.  How much of this will translate to your 4.5
situation is questionable.  Version 7 is much sweeter then earlier versions, in my
opinion, and is worth the upgrade.

Rob Jacobsen
Cowlitz Water Pollution Control Plant
Longview, WA



Tue, 07 Sep 1999 03:00:00 GMT
 Paradox for Windows 4.5 and networking

Quote:

> Hi all. Recently I had to put our paradox database on a server and am
> wondering how this thing works. The manual "Getting Started" says the
> private and working directry should be on local machine. So I set them so.
> PDOXUSER.NET file is on the server as well as data tables and forms and
> other stuff. But if I was to run a form that's originally written for use
> on local machine, I couldn't run it, for paradox reporting tables the form
> is depending on is missing.

> I know this is a real beginner question. But does this mean that, if I was
> to create an application in Paradox whose data is on the server and actual
> Paradox application is on local workstation, all the tables and queries
> has to be on the server as well? What about reliability issues? Someone
> from different department told me that Paradox isn't good with networking
> stuff, like accessing same record on a table from two or more different
> workstation can currupt the database... Could anybody give me some advice
> or explanation?

> Any respons will be appreciated!

> Mahalo,

> Cody

Makoto,

I'm assuming this is Pdox4.5 for Windows not DOS.  You can have your
forms and reports either on the local workstations (a little faster) or
on the server (easier to distribute/maintain).  What is important is
using aliases in the data models of your forms and reports (and don't
forget your queries).  This ensures migrating and scaleability if you
change the backend to a different database and/or location.

For example, if you click on a table in the data model, you may see
":work:" or nothing preceding the table name.  If you define an alias of
say :theData: that points to the data on the server, and reference that
in the data model, there would be no problem opening the form.  When
developing stand-alone, just have :theData: alias point to local drive
directory.  When production time, define the alias to point to your
server directory.  An easy way to change is to have the data path in an
".ini" file and code that reads the .ini file and defines the alias.
You could also distribute odapi config files with the aliases defined.

To easily change your existing forms, define the alias, open the form
and select "Change Table," browse using the alias and save the form.

Regarding corruption, never seen it with two user's trying to access the
same record.  When I have experienced corrupt data it is almost always
due to an abnormal exit from Paradox--be it power hit, locked up
workstation, frustrated user.  But on the bright side, to date never
actually lost any data.  Running Tutility and restructuring tables
usually fixes.  There are other recovery methods, too.

Good luck,

SLHodson



Sun, 12 Sep 1999 03:00:00 GMT
 Paradox for Windows 4.5 and networking

The private directory (for each user) should be on their local machine. The
working directory does not (an probably should not) be on the local
machine. As you point out, if the files are on the server, how does a user
get to the data?

In my environment, each user runs a local copy of paradox (Version 7 - 32
bit). Each user has a private directory on their c: drive.

All datafiles (tables, forms, reports, queries and scripts) and on the
server. Each users machine is set to make g:\paradox the working directory.
This works just fine.

One thing to watch out for the settings for the nertwork control file. You
need to have a directory that  is accesible to all users who care accessing
tables on the network. Paradox keeps track of who is doing what to which
tables,records, etc. If you have 2 users set up to use different network
control files, and then they go after the same table, the best things that
would happen is that one or both would get an error message saying that the
there were 2 network control files in use (an the table could not be
opened). The worst that could happen is that Paradox would lose track of
who was doing what, and allow 2 users to edit the same record (or worse).

In my enviromnent, we have a separate directory that EVERY user has rights
to, and everyone uses that directory for the network control file.

In my opinion, Paradox handles network situations just fine. I have been
using Pdox since version 1 of DOS. The newer Windows versions (5 and 7) are
a lot easier to control in a network setting (in my opinion).



Quote:
> Hi all. Recently I had to put our paradox database on a server and am
> wondering how this thing works. The manual "Getting Started" says the
> private and working directry should be on local machine. So I set them
so.
> PDOXUSER.NET file is on the server as well as data tables and forms and
> other stuff. But if I was to run a form that's originally written for use
> on local machine, I couldn't run it, for paradox reporting tables the
form
> is depending on is missing.

> I know this is a real beginner question. But does this mean that, if I
was
> to create an application in Paradox whose data is on the server and
actual
> Paradox application is on local workstation, all the tables and queries
> has to be on the server as well? What about reliability issues? Someone
> from different department told me that Paradox isn't good with networking
> stuff, like accessing same record on a table from two or more different
> workstation can currupt the database... Could anybody give me some advice
> or explanation?

> Any respons will be appreciated!

> Mahalo,

> Cody



Sun, 12 Sep 1999 03:00:00 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Windows 95 Networking with Paradox 4.5 for DOS

2. PARADOX FOR DOS 4.5 Speed of printing on a Windows 95 network

3. Problems with Paradox 4.5 and WINDOWS NT 4.5

4. Paradox DOS 4.0/4.5 to Paradox for Windows

5. Conversion Paradox 3.5 DOS to Paradox 4.5 Windows

6. Paradox 4.01 DOS and Paradox 4.5 Windows

7. Problem with Windows NT and Paradox for Windows 4.5

8. Running Paradox 4.5 for Dos on a network

9. printing from paradox 4.5 to a network printer

10. Paradox 4.5 DOS and Novell Network Question

11. PAradox 4.5 / 5 Runtime on Network drive

12. Paradox 4.5 Network Locking Problem


 
Powered by phpBB® Forum Software