Using 2007 to open a .dbf and save as an Access 2000 file???

  • Thread starter Thread starter CatherineDiane
  • Start date Start date
C

CatherineDiane

Am I going around the world to get this database from Works into Access 2000???

The problem is I'm having to work on different machines. During the day the
lady I'm trying to help is using Works for the current database. She has
Access 2000 on her machine. There are several queries and a report she wants
to use which I have built for her in 2007 and saved to the compatible 2000
version.

At home, I have a laptop with 2007 and my desktop with 2003.

I saved the works database as the dbase IV file and emailed it to myself to
convert at home. I plan on opening it with 2007 and then using the
compatibility feature to get it back to a 2000 file.

Is there as simpler way? Let me say in advance, I first tried it on her pc
to save the works file and then open it with 2000 right then. It wouldn't
open it. It was the end of the work day so I just emailed myself the file and
planned to do it here.

Thanks In Advance! Catherine
 
CatherineDiane said:
Am I going around the world to get this database from Works into Access
2000???

The problem is I'm having to work on different machines. During the day
the
lady I'm trying to help is using Works for the current database. She has
Access 2000 on her machine.
Click to expand...

OK, I think this is a good start in that she has both products on her one
machine. I think the only way to save yourself a trip to a room with padded
walls is to move the data out of works, and get are using access 2000 for
data entry. In other words, I actually am suggesting that you get the data
out of the works database, and then from that point on stay away from works.

The other problem courses that remember you're not just dealing with data,
but over time you start dealing with reports, queries, and even perhaps some
macros and code, which then makes it really impossible to move the
application between two different database products such as works and access
(we'll certainly be able to move the data, but after certain amount of time
even that will be a painful process).

So you number one goal here is to get her or the people working in a
compatible system that you all can work with.
There are several queries and a report she wants
to use which I have built for her in 2007 and saved to the compatible 2000
version.

At home, I have a laptop with 2007 and my desktop with 2003.

I saved the works database as the dbase IV file and emailed it to myself
to
convert at home. I plan on opening it with 2007 and then using the
compatibility feature to get it back to a 2000 file.
Click to expand...

MS access cannot open a word file, nor can MS access opened a JPEG picture
file that your friend emails to you. In other words as a general rule you
can move data between some applications, but you can't use the application
to directly open different types of files. What this means that is you can't
open the DB file directly with MS access, but you can import the data.

I should point out that MS access does allow you to actually attach to the
dBase file, and not actually import the data and information inside of MS
access (this is called "linking" to the data). it is very similar to opening
the file, but not quite.

However I see little reason to start *linking* to the dBase file, because as
far as I can tell were all on the board to a elimonate the works database
system altogether.

In other words export the data as dBase file (as you said you've just done).

You can now simply inside of MS access click on the External data tab, and
you'll see in the ribbion a section called "import". If you look in that
list you'll see an option to import a dBase file on the ribbion (you might
have to hight the dropdown).

For any realistic management of this type of data, it is a reasonable
approach to keep everything in access 2000 format. since that person seems
to have both the access and works on their machine, I don't think there's
much reason to continue using works except for a ONE tiny import job as your
tempting now to do.

from that point on hopefully we can just assume that the personal use and MS
access, and not bother with works anymore....
 
Back
Top