Migrate to access ... help !!!

I would like some experts-advice ...

I have:
Developed a database in lotus-approach (97), wich is alive and
kicking.
Unfortunaly, this application runs only on a (out-dated) PC with W95
setup/platform.
The current data-tables are stored in DBF-files. The form and reports
are in the seperate 'apr'-files.

I want:
migrate to access ...

Is it possible (wise), both applications manipulate the
tables/records?

How do/can I proceed?

Regards,
Jos

I noticed that nobody answered so far.

Never worked with Lotus Approach, but worked a lot with .dbf files as
DBase. IF the foundaiton is similar:........

Here's my shooting from the hip guess.

Is there any need or great advantage to try to use both application at once?
If not, just move it to Access.

A .dbf file would be the equivalent of an Acess table.

Learn the structure of the tables and the relationships between them in
Lotus Approach.

Import each .dbf into an Access table.

Recreate the relationships, and then create the needed forms, queries and
reports in Access.

On Thu, 23 Jul 2009 12:13:01 -0700, =?Utf-8?B?RnJlZA==?=
wrote:

Hi fred,


Is there any need or great advantage to try to use both application at once?
If not, just move it to Access.


Honestly ... I have no idea.

I'm 'brandnew' to access, and my 'learning-curve' is not so steep as
it used to be ... so the current application has to keep running,
while new data comes in.

What is the best approach to migrate the acces database?

I think, My scenario looks like this:
* Take a 'picture' of the current tables, and develop on these copies
the acces forms and reports.
* In the meantime, keep the tables uptodate with the lotus-approach
application.
* When acces is 'ready', I need a method to 're-import' the updated
tables.

One of my (many) concerns is the 'autonumber fields' which are
generated with lotus (sequentially), The algoritm will probably differ
from access. These fields are used as link between the tables.

If access takes over, will the generated 'autonumbers' fit in the
excisting ones?

In message , "John@home"
writes
On Thu, 23 Jul 2009 12:13:01 -0700, =?Utf-8?B?RnJlZA==?=
wrote:

Hi fred,


Is there any need or great advantage to try to use both application at once?
If not, just move it to Access.


Honestly ... I have no idea.

I'm 'brandnew' to access, and my 'learning-curve' is not so steep as
it used to be ... so the current application has to keep running,
while new data comes in.

What is the best approach to migrate the acces database?

The first step is to decide how you will know that the new Access
application does everything that you need. Only at that point will it be
safe to switch over. Decide on the tests that you will apply.



I think, My scenario looks like this:
* Take a 'picture' of the current tables, and develop on these copies
the acces forms and reports.

That's probably the best option. At this early stage you may also want
to consider whether the table structure that you have is right, or
whether it needs to be changed.

There are two ways that you can take a picture of the existing data.
Firstly you can import the data into an Access database, each .DBF file
becomes a new table. Secondly you can link your .DBF files to Access
tables, Access will be able to read and write data in .DBF format.

Both of these options have advantages and disadvantages. Whatever route
you choose, make sure that you only work with a copy of your original
data up until the point that the new system goes live. Keep the original
data safe.

* In the meantime, keep the tables uptodate with the lotus-approach
application.
* When acces is 'ready', I need a method to 're-import' the updated
tables.

That's relatively simple if you have retained the database structure
from the Approach system. If you have changed the structure then you
will have an additional transformation step that converts the old data
to its new structure.


One of my (many) concerns is the 'autonumber fields' which are
generated with lotus (sequentially), The algoritm will probably differ
from access. These fields are used as link between the tables.

In general it doesn't matter what algorithm is used as long as it always
generates a unique number. One little gotcha is that in some situations
Access can skip over an autonumber value. You should not rely on having
an unbroken sequence of numbers.


If access takes over, will the generated 'autonumbers' fit in the
excisting ones?

That is certainly possible. If you convert an existing field to an
autonumber Access will take the highest existing number and start adding
1 to it each time you create a new record.




--
Bernard Peek

How have you come to the conclusion that Access is the tool you need to use?

Regards

Jeff Boyce
Microsoft Office/Access MVP

"John@home" wrote in message
...
I would like some experts-advice ...

I have:
Developed a database in lotus-approach (97), wich is alive and
kicking.
Unfortunaly, this application runs only on a (out-dated) PC with W95
setup/platform.
The current data-tables are stored in DBF-files. The form and reports
are in the seperate 'apr'-files.

I want:
migrate to access ...

Is it possible (wise), both applications manipulate the
tables/records?

How do/can I proceed?

Regards,
Jos

What the heck, go for it. ! :-)

Assuming that implicit in your "migrate" question is "migrate and have a
good thing going", one of the big questions that will determine answers and
what you'll be doing is What is the quality level of your table structure
and data? Is it normalized? Are there data definition, for the contents of
tables and fields which have been followed?

Either way, an important early step will be to assess and learn what you
currently have regarding items I asked about.

On Thu, 23 Jul 2009 17:02:48 -0700, "Jeff Boyce"
wrote:

How have you come to the conclusion that Access is the tool you need to use?

Regards

Jeff Boyce
Microsoft Office/Access MVP


Not really an conclusion, it's an option.
Perhaps, an other option is to go for a 'dual-boot' system. (new OS
and W95)
I'm assessing both options ... Hence my quest for access-experts
insight.

It seems the logical way to go for access (compatibility for the
future)
This database is used for my personal use (non-profit ... So I've not
a lot of money at my disposal)

Access looks like the 'defacto' database-standard. Support is plenty
around. And access will have support together with the (future)
operating systems.

Although, approach is an excellent tool for my 'simpel' mind, the
support is minimal.

The lotus approach97 application run's only smooth on a W95 platform.
The current PC is 12 years old and need to be replaced (before it
crashes).
If I buy uptodate hardware, I need to buy an upgraded approach-version
as well. But then again ... I will encounter the same issue/question
within time.

Regards,
Jos

I'm not familiar with the Lotus offering, so I don't know the degree of
'match' with Access.

I usually offer 4 learning curves that will need to be surmounted before you
can develop a useful (i.e., gets used!) application. You may have already
surmounted all 4:

1. Relational database design/normalization
2. Access tips/tricks
3. Graphical User Interface design
4. Application development

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

"John@home" wrote in message
...
On Thu, 23 Jul 2009 17:02:48 -0700, "Jeff Boyce"
wrote:

How have you come to the conclusion that Access is the tool you need to
use?

Regards

Jeff Boyce
Microsoft Office/Access MVP


Not really an conclusion, it's an option.
Perhaps, an other option is to go for a 'dual-boot' system. (new OS
and W95)
I'm assessing both options ... Hence my quest for access-experts
insight.

It seems the logical way to go for access (compatibility for the
future)
This database is used for my personal use (non-profit ... So I've not
a lot of money at my disposal)

Access looks like the 'defacto' database-standard. Support is plenty
around. And access will have support together with the (future)
operating systems.

Although, approach is an excellent tool for my 'simpel' mind, the
support is minimal.

The lotus approach97 application run's only smooth on a W95 platform.
The current PC is 12 years old and need to be replaced (before it
crashes).
If I buy uptodate hardware, I need to buy an upgraded approach-version
as well. But then again ... I will encounter the same issue/question
within time.

Regards,
Jos

On Fri, 24 Jul 2009 07:48:46 -0700, "Jeff Boyce"
wrote:


I usually offer 4 learning curves that will need to be surmounted before you
can develop a useful (i.e., gets used!) application. You may have already
surmounted all 4:

1. Relational database design/normalization

The structure is solid and tables are normalised

2. Access tips/tricks

Thats, where you guys kicks in ... )


3. Graphical User Interface design
4. Application development

That will be my time-consumer. Learn how 'things' are accomplisched in
access. it's a lot harder (for me) to crack, then approach ...


Good luck!


Thanks ... time will tell.

Hello Jos,

Do you want help migrating to Access? If you can send me a listing of your
tables and fields in each table, I could create Access tables for your data
and then build the forms for entering data. I wouldn't need to see your
lotus-approach forms; I could build the Access forms from just looking at
the tables. Regarding reports, if you can send me a screen shot of your
lotus-approach reports, I would be able to create Access reports that
display the same information as your lotus-approach reports. Otherwise, if
you can give me a detailed description of each of your existing reports, I
would be able to create Access reports that display the information you
describe for each report. We would work together to give you an Access
database that is "alive and kicking". The end result would be an Access
database containing all the lotus-approach data and with the same
functionality as your existing lotus-approach database. You would be able to
see how an Access database is setup and an application is created. You would
gain a good background for building future Access applications. My fee to
work with you would be very reasonable.

Steve






"John@home" wrote in message
...
I would like some experts-advice ...

I have:
Developed a database in lotus-approach (97), wich is alive and
kicking.
Unfortunaly, this application runs only on a (out-dated) PC with W95
setup/platform.
The current data-tables are stored in DBF-files. The form and reports
are in the seperate 'apr'-files.

I want:
migrate to access ...

Is it possible (wise), both applications manipulate the
tables/records?

How do/can I proceed?

Regards,
Jos