Your company might do better by hiring some Paradox expertise. Especially
if this ap is in any way important to the company. What they are doing now
is basically the same as asking a secretary to take over bookkeeping
because she sometimes uses a calculator. Might work. Not likely. There are
lots of consulting organizations out there (such as ours, of course, and
others you can find at thedbcommunity.com) who can help you.
Nevertheless, see in line.
> I'm basically a developer using Access. The company that I work for
> has a paradox database that was developed about 7 years ago. The
> developer is no longer working for the company. The database is
> starting to generate errors
Starting to? Since when? What changed? Paradox aps don't just start
modifying themselves any more than other aps. So either the problem has
been there or something is different now.
Quote:> and there is no documentation what so ever
With any luck at least the code is commented. But learning OPAL is going
to turn your head around a bit if you are only used to Access.
> and no one in the company has any paradox experience. So I've been
> volunteered to try and figure out what the problem might be. So any
> help would be greatly appreciated!!!
> There is a problem with some records occasionally being deleted from
> certain tables. It appears that when a certain process is done this
Well, what process? And does it always delete records? The same records?
Random Records? What pattern are you seeing? Can you reproduce the
problem? Are you certain this is not what it is supposed to do?
Quote:> My first plan of attack would be to repair tables.
Record deletions are not likely the result of table damage. Repair won't
bring the records back. But verifying the integrity of the tables won't
hurt. Make copies of all the tables (and their associated parts) before
you start. Paradox does not use a single monolithic table like the MDB.
Each table is multipart consisting of at least a .db and usually a .px
(primary index), .val, and any number of secondary indices. See the
Paradox help for a list of file extensions. Failure to capture all the
current parts of a table (other than FAM and TV) can break a table.
Quote:> I see
> that there is a repair procedure in the menu. Each table has to be
> repaired individually?
Quote:> Do you think this might fix the problem or can
> it be something more serious?
Doubtful it will fix the problem. Serious is a relative thing. It might be
something very simple. It might be a simple misunderstanding of how the ap
is supposed to work. We would need to know a lot more about the ap and the
deletions to answer the question.
Quote:> Also I can't get the forms in design
> mode, is there a way that I can unlock the forms so I can put it in
> design mode?
You need the undelivered versions (FSL rather than FDL). If you don't have
the ?SL files for your forms, reports, libraries and scripts you are stuck
as you can not modify a delivered (compiled) form.
Quote:> Also is it possible that the forms can be exported into Access? I've
> read in a document that this can be done.
No. There is no such conversion utility. Data can be exported (or read
natively) but not the programming. They work too differently.
Quote:> I pretty much have my back against the wall here, any help would be
> greatly appreciated. I'm off to a local store to buy a paradox book
> for some in-depth reading...lol.
Talk to your bosses about getting real help Using the wrong tool for the
job is a bad idea under pretty much all circumstances. Paradox can do
whatever you need but you have to know how to develop in it. Of course
there is no guarantee the original developer did. Lots of people say they
are database developers (in any tool) and really have no clue about
database design. You may want to check out my paper "Hammering Screws" on
our Paradox resources page (link in my signature). You might want to pass
it on to your boss as well. To get yourself started on learning Pdox (if
you must go that route) I suggest you start with my "Database Basics"
paper also on the Paradox resources page. It can help you with info on
pitfalls and best practices. As for books, there are lots of good ones out
there (ones for as far back as version 7 will still be very helpful and to
version 5 are useful) but you will likely have to hunt them down at used
places. Some good ones are also listed at thedbcommunity.com.
Best of luck.
Resource Development Associates
Offices in the United States and Germany
Providing solutions to health care, business, governments and non-profits