Re: Overview of Paradox database structure and architecture
- From: "Leslie Milburn" <CDB4W@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 2 Aug 2008 11:03:55 +1000
Hi Michelle,
I always understood the question to be basically about data migration but I
can also see that based upon the phrasing used it was probably more,
otherwise the OP would know to just open the tables directly in ACCESS and
copy them over and then work fully within the environment he is comfortable
with. Hence no issue in any case.
BUT, in some projects that will not be enough. I have worked on projects
especially older ones where data *not* being present meant something. In
order to know under which scenarios data would not be present required
access to the business rules. To read the business rules in P4W would
require navigational knowledge in order to locate the code in the first
place (Not usually centrally located in older apps), and then you would need
to be fairly proficient in OPAL to then read the code etc.
In other words there is a difference between transference of data and system
replacement, just like there is a difference between a Business Analyst and
a Systems Analyst, close but maybe not close enough.
I should also point out that my tone was clear and concise and he can take
it or leave it. BUT know this, a good interviewer cannot be fooled and it
really is that simple. If the OP is comfortable with his approach then I for
one do not care and I wish him well.
Leslie.
"Michelle Burnore" <michelljb@xxxxxxx> wrote in message
news:4893919f$1@xxxxxxxxxxxxxxxxxxxxxxxxxxx
All your questions are very valid, Steve, and no, I know that would not be
enough for anyone to use Paradox. The point, I think, is that the client
wants someone who knows Access, and can convert Paradox tables to it. He
didn't mention anything about having to dig into code, so I am not
assuming that is the case. If he DOES have to convert OPal into Access
Basic (although why in the world would you?), then you are right. Basic
info on file types was all he asked for. If his questions start going
deeper, than we'll go deeper.
I've been programming in Paradox DOS for 20 years and in Paradox Windows
for 13. There isn't any way to learn that stuff and get proficient at it
in the time span he has, which is why I was assuming he didn't need to go
that deep.
I had no problem with you guys cautioning him that he might be in over his
head. I don't think he did either. The problem was the tone used and the
accusations that came with it.
~Michelle
.
- Follow-Ups:
- Re: Overview of Paradox database structure and architecture
- From: Michelle Burnore
- Re: Overview of Paradox database structure and architecture
- From: Leslie Milburn
- Re: Overview of Paradox database structure and architecture
- References:
- Re: Overview of Paradox database structure and architecture
- From: Dominick DiMantova
- Re: Overview of Paradox database structure and architecture
- From: Leslie Milburn
- Re: Overview of Paradox database structure and architecture
- From: Michelle Burnore
- Re: Overview of Paradox database structure and architecture
- From: Steven Green
- Re: Overview of Paradox database structure and architecture
- From: Michelle Burnore
- Re: Overview of Paradox database structure and architecture
- Prev by Date: Re: Overview of Paradox database structure and architecture
- Next by Date: Re: Overview of Paradox database structure and architecture
- Previous by thread: Re: Overview of Paradox database structure and architecture
- Next by thread: Re: Overview of Paradox database structure and architecture
- Index(es):
Relevant Pages
|