Overview of Paradox database structure and architecture

OK, thanks. Is it possible that there is a diagram of a typical paradox database
structure, with its tables, stuff like that?




Robert Molyneux wrote:
>Dominick DiMantova wrote:
>> Hello, I would like to know if I can get an overview of a paradox database
>> structure and architecture? I'm applying for a migration position that
requires
>> familiarity with paradox database structure. Can someone help me by sending
>> documentation to my email account, dominickdimantova-at-comcast.net? I really
>> would appreciate this.
>>
>>
>>
>It is a file-based Relational Database Management System. That is, the
>RDBMS tables and their various metadata and indices are held as lots of

>files, rather than the single large file / all eggs in one basket of
>Bill's boys pathetic offerings... (but I digress...)
>
>You can use Paradox to inspect all tables and their fields, as well as
>relational integrity constraints and meta-data.
>
>Provided that your database has been properly designed, you will (a)
>understand the wonderful nature of a properly designed RDBMS and (b)
>question why you would want to migrate from it.
>
>All business rules (unfortunately) are held in the application code
>(Pascal look-alike called OPAL) and (obscure) table-driven components.
>
>Thus, you may seek the long-gone and (deservedly) dead developers to
>attempt to strangle them.
>

>As for 'rude', people looking for shortcuts to fool potential
>employers probably should expect rude or worse.

Nope, just wanting to be familiar with paradox database structure, as there
is a position to migrate paradox database into an Access database and the
client wants someone who is familiar with paradox structure. Not trying to
cheat.





"Tony McGuire" wrote:
>
>> I'm basically asking for a short
>
>You have 'tables', where data is stored.
>
>In the tables you have rows, which are called 'records'. And you have
>'cells', which are called 'fields'.
>
>What more are you looking for?
>
>
>I think adding in the subject title 'architecture' is where the issue
>lies. That would normally be a deep technical look; Borland hasn't
>released anything on 'architecture'.
>
>As for 'rude', people looking for shortcuts to fool potential
>employers probably should expect rude or worse.
>
>--
>------------------------------
> Tony McGuire
>
>

> OK, thanks. Is it possible that there is a diagram of a typical
> paradox database
> structure, with its tables, stuff like that?

There IS no 'typical paradox database structure'.

Each table is independent (generally), but can be linked in forms
(views) and reports (print output).

Every developer sets things up their own way. So you need THEIR map
of how things are designed.

Or run the forms that are designed to work with the tables and figure
it out manually; better would be if you have the source files of the
forms and reports, and you can get the 'datamodel' of them with a copy
of Paradox.

Your 'familiarity' request is a much deeper question than a simple
question, particularly if you want it as part of a job you'll be paid
for. Likely you'll need a LOT of familiarity if you'll just be given
a set of tables and asked to create a database in Access with correct
links and such.


--
------------------------------
Tony McGuire

> Not trying to cheat.

you ARE thrying to cheat.. if you knew the basics, you wouldn't be here..

--
Steven Green - Myrtle Beach, South Carolina USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

"Dominick DiMantova" wrote in message
news:4891cc58$1-at-pnews.thedbcommunity.com...
>
>>As for 'rude', people looking for shortcuts to fool potential
>>employers probably should expect rude or worse.
>
> Nope, just wanting to be familiar with paradox database structure, as
> there
> is a position to migrate paradox database into an Access database and the
> client wants someone who is familiar with paradox structure. Not trying to
> cheat.
>
>
>
>
>
> "Tony McGuire" wrote:
>>
>>> I'm basically asking for a short
>>
>>You have 'tables', where data is stored.
>>
>>In the tables you have rows, which are called 'records'. And you have
>>'cells', which are called 'fields'.
>>
>>What more are you looking for?
>>
>>
>>I think adding in the subject title 'architecture' is where the issue
>>lies. That would normally be a deep technical look; Borland hasn't
>>released anything on 'architecture'.
>>
>>As for 'rude', people looking for shortcuts to fool potential
>>employers probably should expect rude or worse.
>>
>>--
>>------------------------------
>> Tony McGuire
>>
>>
>

You know what, I don't have the patience to deal with you, you idiot. I'm
not going to explain anything further to you. Go away and don't respond to
me again.

"Steven Green" wrote:
>> Not trying to cheat.
>
>you ARE thrying to cheat.. if you knew the basics, you wouldn't be here..
>
>--
>Steven Green - Myrtle Beach, South Carolina USA
>
>Diamond Software Group
>http://www.diamondsg.com/main.htm
>Paradox Support & Sales
>
>Diamond Sports Gems
>http://www.diamondsg.com/gemsmain.htm
>Sports Memorabilia and Trading Cards
>
>"Dominick DiMantova" wrote in message
>news:4891cc58$1-at-pnews.thedbcommunity.com...
>>
>>>As for 'rude', people looking for shortcuts to fool potential
>>>employers probably should expect rude or worse.
>>
>> Nope, just wanting to be familiar with paradox database structure, as

>> there
>> is a position to migrate paradox database into an Access database and
the
>> client wants someone who is familiar with paradox structure. Not trying
to
>> cheat.
>>
>>
>>
>>
>>
>> "Tony McGuire" wrote:
>>>
>>>> I'm basically asking for a short
>>>
>>>You have 'tables', where data is stored.
>>>
>>>In the tables you have rows, which are called 'records'. And you have
>>>'cells', which are called 'fields'.
>>>
>>>What more are you looking for?
>>>
>>>
>>>I think adding in the subject title 'architecture' is where the issue
>>>lies. That would normally be a deep technical look; Borland hasn't
>>>released anything on 'architecture'.
>>>
>>>As for 'rude', people looking for shortcuts to fool potential
>>>employers probably should expect rude or worse.
>>>
>>>--
>>>------------------------------
>>> Tony McGuire
>>>
>>>
>>
>
>

So, I gather that there is no quick way to get an overview of a paradox database
system, like a diagram of its structure, such as tables, relationships between
tables, etc.? I just want to talk intelligently about it during a possible
interview that calls for one to migrate a paradox database into an Access
database.




"Tony McGuire" wrote:
>
>> OK, thanks. Is it possible that there is a diagram of a typical
>> paradox database
>> structure, with its tables, stuff like that?
>
>There IS no 'typical paradox database structure'.
>
>Each table is independent (generally), but can be linked in forms
>(views) and reports (print output).
>
>Every developer sets things up their own way. So you need THEIR map
>of how things are designed.
>
>Or run the forms that are designed to work with the tables and figure
>it out manually; better would be if you have the source files of the
>forms and reports, and you can get the 'datamodel' of them with a copy
>of Paradox.
>
>Your 'familiarity' request is a much deeper question than a simple
>question, particularly if you want it as part of a job you'll be paid
>for. Likely you'll need a LOT of familiarity if you'll just be given
>a set of tables and asked to create a database in Access with correct
>links and such.
>
>
>--
>------------------------------
> Tony McGuire
>
>

> So, I gather that there is no quick way to get an overview of a paradox
> database system, like a diagram of its structure, such as tables,
> relationships between tables, etc.?

is every Access app the same? of course not.. so why do you expect every
Paradox app to be the same?.. you think we're idiots, but you're missing the
main point.. if you really knew enough about Access apps and programming,
you'd know the scope of what you'd have to know in another platform.. and
obviously, you don't..

you don't have the tools for the job you're applying for.. if you did, you
wouldn't be here..

--
Steven Green - Myrtle Beach, South Carolina USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

"Dominick DiMantova" wrote in message
news:4891d0e1$1-at-pnews.thedbcommunity.com...
>
> So, I gather that there is no quick way to get an overview of a paradox
> database
> system, like a diagram of its structure, such as tables, relationships
> between
> tables, etc.? I just want to talk intelligently about it during a possible
> interview that calls for one to migrate a paradox database into an Access
> database.
>
>
>
>
> "Tony McGuire" wrote:
>>
>>> OK, thanks. Is it possible that there is a diagram of a typical
>>> paradox database
>>> structure, with its tables, stuff like that?
>>
>>There IS no 'typical paradox database structure'.
>>
>>Each table is independent (generally), but can be linked in forms
>>(views) and reports (print output).
>>
>>Every developer sets things up their own way. So you need THEIR map
>>of how things are designed.
>>
>>Or run the forms that are designed to work with the tables and figure
>>it out manually; better would be if you have the source files of the
>>forms and reports, and you can get the 'datamodel' of them with a copy
>>of Paradox.
>>
>>Your 'familiarity' request is a much deeper question than a simple
>>question, particularly if you want it as part of a job you'll be paid
>>for. Likely you'll need a LOT of familiarity if you'll just be given
>>a set of tables and asked to create a database in Access with correct
>>links and such.
>>
>>
>>--
>>------------------------------
>> Tony McGuire
>>
>>
>

This was such a beautiful day until now. Sorry to bring this rant to the
group, but since this person is playing a little game here, I thought others
might appreciate seeing the "original" email that this guy sent to me after
my posting.
**************
-----Original Message-----
From: Dominick [mailto:dominickdimantova-at-comcast.net]
Sent: Thursday, July 31, 2008 10:35 AM
To: Giner, Jim
Subject: My response to your idiot response from the comp.databases.paradox
discussion group


In case you missed my response to your idiotic, moronic response, here it
is. OH, btw, I have blocked you out so that I don't get messages from you,
if you try to respond to comcast email account.


You are obviously a moron, MORON! Read my question from my first post,
dumbass;
I'm asking a question, in the hopes that can get a brief overview of paradox
structures, so that I can successfully migrate paradox tables, and other
objects, into an Access database. I was aware that SOME idiots, like you,
do not possess the mental facilities to understand my first question. Do me
a favor, pal, do not respond to my messages again, got it? I don't have the
patience to deal with idiots like you.

************
That was in my personal in-box. I hope everyone sees what this guy (who
according to more than one of us is cheating) is capable of doing.
Obviously he wasn't proud enough of his writing to put 'all' of his feelings
into the group post.

I see from other's responses that I wasn't the only one to misconstrue his
question and since I see that others feel that what he is doing is wrong, I
do not regret my earlier message one iota. What a hot head - and he blocks
me! Boy - is that backwards!

I pity the guy he works for....

>you don't have the tools for the job you're applying for.. if you did, you

>wouldn't be here..

You don't know me, fool. What I DO now know is that, out of all of the responses
that I've gotten about my first posting, two or three of you, gave me good
responses and I appreciate that. The rest, like this idiot Steven Green,
along with this other idiot, Jim Giner, are all STUPID! and I don't want
to hear from any of them. Just the two, or three, who gave me decent answers
to my first question. But, I shall re-iterate, for the sake of Steven Green
and Jim Giner, who doesn't have the mental faculties to understand what I'm
talking about: I applied for a position, using my MS Access experiences and
skills, to migrate a Paradox database into an Access database. Now, I don't
know a thing about paradox, but, using my Access expertise, I feel, if I
can get a quick understanding of Paradox database objects, like tables, relationships,
keys, etc., I can talk intelligently about paradox during a possible interview.
These two fools, and I won't name names, think I'm trying to cheat my into
a job. Now, Mr. Green, do you THINK you can understand what I was saying?
If not, try doing some brain exercises and let me know how you are coming
along .




"Steven Green" wrote:
>> So, I gather that there is no quick way to get an overview of a paradox

>> database system, like a diagram of its structure, such as tables,
>> relationships between tables, etc.?
>
>is every Access app the same? of course not.. so why do you expect every

>Paradox app to be the same?.. you think we're idiots, but you're missing
the
>main point.. if you really knew enough about Access apps and programming,

>you'd know the scope of what you'd have to know in another platform.. and

>obviously, you don't..
>
>you don't have the tools for the job you're applying for.. if you did, you

>wouldn't be here..
>
>--
>Steven Green - Myrtle Beach, South Carolina USA
>
>Diamond Software Group
>http://www.diamondsg.com/main.htm
>Paradox Support & Sales
>
>Diamond Sports Gems
>http://www.diamondsg.com/gemsmain.htm
>Sports Memorabilia and Trading Cards
>
>"Dominick DiMantova" wrote in message
>news:4891d0e1$1-at-pnews.thedbcommunity.com...
>>
>> So, I gather that there is no quick way to get an overview of a paradox

>> database
>> system, like a diagram of its structure, such as tables, relationships

>> between
>> tables, etc.? I just want to talk intelligently about it during a possible
>> interview that calls for one to migrate a paradox database into an Access
>> database.
>>
>>
>>
>>
>> "Tony McGuire" wrote:
>>>
>>>> OK, thanks. Is it possible that there is a diagram of a typical
>>>> paradox database
>>>> structure, with its tables, stuff like that?
>>>
>>>There IS no 'typical paradox database structure'.
>>>
>>>Each table is independent (generally), but can be linked in forms
>>>(views) and reports (print output).
>>>
>>>Every developer sets things up their own way. So you need THEIR map
>>>of how things are designed.
>>>
>>>Or run the forms that are designed to work with the tables and figure
>>>it out manually; better would be if you have the source files of the
>>>forms and reports, and you can get the 'datamodel' of them with a copy
>>>of Paradox.
>>>
>>>Your 'familiarity' request is a much deeper question than a simple
>>>question, particularly if you want it as part of a job you'll be paid
>>>for. Likely you'll need a LOT of familiarity if you'll just be given
>>>a set of tables and asked to create a database in Access with correct
>>>links and such.
>>>
>>>
>>>--
>>>------------------------------
>>> Tony McGuire
>>>
>>>
>>
>
>

Dominick,

There are numerous structures for Paradox, but these are the most common.

*.Database - This is the physical table that contains your records. It looks
virtually identical to an Access table.

*.PX - If the table is keyed (same principle as in Access), there will
be a file by the same name as the table with this extension.

*.XG0, *.YG0, etc. - If there are secondary indexes on the table, there
will be files with these or similar extensions.

From within Paradox Windows, you can open the Project Viewer which
lists Tables, Forms, Queries, Reports, etc. just as an MB file in Access
will.

Hope that helps,

Michelle