Overview of Paradox database structure and architecture

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.

If you mean the internals they are not public (nor published AFAIK). If
you mean how does paradox work or how are tables structured, thats a lot
to learn. As for sending to your private mail, that isn't how the groups
work.

Feel free to ask questions here. We'll try and answer them here.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

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.
>
>
>

> I'm applying for a migration position that requires familiarity with
> paradox database structure.

but obviously, you have none.. if it was that easy, everyone would be a
database expert..

most of us here have been doing this for 10 to 20 years.. how much of that
knowledge do you expect to absorb in 5 minutes?

--
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:48908141$1-at-pnews.thedbcommunity.com...
>
> 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.
>
>
>

Dominick DiMantova wrote:

> Hello, I would like to know if I can get an overview of a paradox database
> structure and architecture?

I assume you mean Paradox application structure and architecture, e.g., what
are typically the various pieces of a typical Paradox app, how do they fit
together, and how do you begin to digest such a thing.

If that's the case, then it matters to ask, DOS or Windows? Very different
beasts.

Steve has a point in that a little knowledge can be a dangerous thing. Be
advised that poorly documented, poorly structured, poorly conceived Paradox
apps are very common, typically consisting of hundreds of tables and
development artifacts (many unused, the result of ad hoc analysis or aborted
development) with little rhyme or reason, or worse - dumped into a single
directory. Going in to something like that with little or no experience in
this is often less desirable than a few extra months' unemployment. :-)

Out of curiosity, what is the migration target platform/language?

--
Larry DiGiovanni

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.

Great Answer Steve! I'm appalled that a person is trying to "cheat" his way
into a new job by doing a quick canvas of an experts group to try and fool a
potential employer into hiring him on a smattering of knowledge.
Dare I even guess that his use of the word "migration" is incorrect and he
may have meant "immigration"? That would be even worse!
"Steven Green" wrote in message
news:4890a512$1-at-pnews.thedbcommunity.com...
>> I'm applying for a migration position that requires familiarity with
>> paradox database structure.
>
> but obviously, you have none.. if it was that easy, everyone would be a
> database expert..
>
> most of us here have been doing this for 10 to 20 years.. how much of that
> knowledge do you expect to absorb in 5 minutes?
>
> --
> 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:48908141$1-at-pnews.thedbcommunity.com...
>>
>> 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.
>>
>>
>>
>
>

Uh, excuse me, aren't we being rude here??? I'm basically asking for a short
overview of a paradox database structure--nothing fancy; just a brief overview.
Is that asking too much?



"Steven Green" wrote:
>> I'm applying for a migration position that requires familiarity with
>> paradox database structure.
>
>but obviously, you have none.. if it was that easy, everyone would be a

>database expert..
>
>most of us here have been doing this for 10 to 20 years.. how much of that

>knowledge do you expect to absorb in 5 minutes?
>
>--
>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:48908141$1-at-pnews.thedbcommunity.com...
>>
>> 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.
>>
>>
>>
>
>

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 questio. 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.


"Jim Giner" wrote:
>Great Answer Steve! I'm appalled that a person is trying to "cheat" his
way
>into a new job by doing a quick canvas of an experts group to try and fool
a
>potential employer into hiring him on a smattering of knowledge.
>Dare I even guess that his use of the word "migration" is incorrect and
he
>may have meant "immigration"? That would be even worse!
>"Steven Green" wrote in message
>news:4890a512$1-at-pnews.thedbcommunity.com...
>>> I'm applying for a migration position that requires familiarity with

>>> paradox database structure.
>>
>> but obviously, you have none.. if it was that easy, everyone would be
a
>> database expert..
>>
>> most of us here have been doing this for 10 to 20 years.. how much of
that
>> knowledge do you expect to absorb in 5 minutes?
>>
>> --
>> 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:48908141$1-at-pnews.thedbcommunity.com...
>>>
>>> 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.
>>>
>>>
>>>
>>
>>
>
>

> 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

Well, I may be asked to migrate paradox database objects into an Access database
and I just want a brief overview of the paradox database, so that, in a possible
interview, at least I can say something intelligent about paradox that would
enhance my chances, with my Access background, for getting this contract
assignment.




"Larry DiGiovanni" wrote:
>Dominick DiMantova wrote:
>
>> Hello, I would like to know if I can get an overview of a paradox database
>> structure and architecture?
>
>I assume you mean Paradox application structure and architecture, e.g.,
what
>are typically the various pieces of a typical Paradox app, how do they fit
>together, and how do you begin to digest such a thing.
>
>If that's the case, then it matters to ask, DOS or Windows? Very different
>beasts.
>
>Steve has a point in that a little knowledge can be a dangerous thing.
Be
>advised that poorly documented, poorly structured, poorly conceived Paradox
>apps are very common, typically consisting of hundreds of tables and
>development artifacts (many unused, the result of ad hoc analysis or aborted
>development) with little rhyme or reason, or worse - dumped into a single
>directory. Going in to something like that with little or no experience
in
>this is often less desirable than a few extra months' unemployment. :-)
>
>Out of curiosity, what is the migration target platform/language?
>
>--
>Larry DiGiovanni
>
>