Re: Using Access 97 with Project

From: Earl Lewis (Earldotlewisatutahdotedu)
Date: 03/07/05 

Date: Mon, 7 Mar 2005 14:41:54 -0700

Kahuna,

I'd have to take issue with the statement about stability of A97 vs. later versions. I agree that A97 was a huge improvement in stability over prior versions but all later releases of Access were improvements over A97 as well.

What kind of stability concerns do you have about later versions? I've done plenty of fairly intensive development projects in A2k and A2k2 and had no "stability" issues that I couldn't resolve.

If stability is your only reason for sticking with A97 on this project I think you should re-evaluate - and save yourself lots of database version compatibilty problems in the process. ;>)

Earl

>>> Kahuna<none@gonewest.com> 3/7/2005 2:15:01 PM >>>
Thanks for the feedback Jack.

Fraid A97 is still he most stable Access available and DAO is our preferred
data model. So no chance of changing just yet. Need instead to find a method
of Project Interaction that works across the board (A97 / MSP 2k - 04).

Cheers 

-- 
Kahuna
------------
"JackD" <momokuri@gmail> wrote in message 
news:uvrhTu0IFHA.1948@TK2MSFTNGP14.phx.gbl...
> More comments in line
>
> -- 
> -Jack  ... For project information and macro examples visit
> http://masamiki.com/project 
>
> .
> "Earl Lewis" <Earldotlewisatutahdotedu> wrote in message
> news:OREdZ7zIFHA.2356@TK2MSFTNGP12.phx.gbl...
>> See comments in-line.
>>
>> Earl
>>
>> >>> Kahuna<none@gonewest.com> 3/7/2005 10:13:27 AM >>>
>> Thanks for that feedback Earl.
>>
>> Couple of questions if you've time to respond:
>>
>> >1. Can the MSP(say)2002 then read the A97 database after its converted?
>>
>> Project 2003 seems to be fine with READING an Access 97 mdb. Don't know
> how it will react to writing.
>
> With Proj 2k if the existing db is 97 it can write to it. It can not 
> create
> an access 97 database though. I think this should be the same for proj 
> 2003,
> but can't be sure. The transition from access 97 to 2000 was very messy. I
> recall that in some cases if a 97 db was opened in Access 2000 it would be
> irrevocably converted and 97 users could not open it again.
>
>> >I ask this because what I really need to do is write the data to the
> tables
>> >from my A97 app and have them read by MSP.  There may be some 
>> >interaction
>> >also where the user changes the content (start dates etc) in MSP and 
>> >that
>> >needs to be readable again by my app.
>>
>> >2. Is it possible to keep the Db created with MSP in A2k format and link
> to
>> >those table through A97 using an ODBC driver?
>
> I think you want to get away from A97 if you can.
>
>> >As an aside - my app runs in RunTime, and is a split Back/Front End but
> with
>> >numerous other library / support Db's. It's my intention to make one of
>> >these specific to the Scheduling data for use in MSP. Also A2k or any
> other
>> >Access version may not be installed on the users box.
>>
>> You'd only need Access 2000 or greater to conver the initial mdb from A2k
> format to A97. Then the clients can be all A97 from then on out.
>>
>> -- 
>> Kahuna
>> ------------
>> "Earl Lewis" <Earldotlewisatutahdotedu> wrote in message
>> news:ejhZ%23bzIFHA.4092@tk2msftngp13.phx.gbl...
>> > Kahuna,
>> >
>> > Forgot one important thing. You'll probably have to add a step to your
>> > process that converts the database created by project to Access 97
> format
>> > after it is generated. MSPorject Pro 2002 and 2003 create Access 2000
>> > format mdbs and they won't open in Access 97. This can be automated in
>> > Access 2000, 2002 or 2003 if you like. An Access one-liner would be
>> > something like this:
>> >
>> > Public Sub ConvertTo97(strOrigFile As String, strAccess97File As 
>> > String)
>> >    Application.ConvertAccessProject strOrigFile, strAccess97File,
>> > acFileFormatAccess97
>> > End Sub
>> >
>> > Earl
>> >
>> >>>> Earl Lewis<Earldotlewisatutahdotedu> 3/7/2005 9:28:31 AM >>>
>> > Kahuna,
>> >
>> > Basically, you take the same approach as you did before, save the
> project
>> > files as Access databases. The problem with this approach is that
> Project
>> > wants to create one Access database for every project. I suppose you
> could
>> > create a "Project Open" routine that asks the user to select which mdb
> to
>> > open when you start up your application.
>> >
>> > This architecture would be a very good reason to use the MSAccess
> "split"
>> > database design where you create the user interface elements (queries,
>> > forms, reports) as one mdb and all the data files are kept in separate
>> > mdb's and pointed to as required by the user.
>> >
>> > If you have any more questions about this reply let me know or check 
>> > out
>> > the ms.public.acess newsgroups.
>> >
>> > Earl
>> >
>> >>>> Kahuna<none@gonewest.com> 3/6/2005 12:27:37 PM >>>
>> > Hi folks
>> >
>> > Many moons ago I used A97 to control a linked database which was also
> used
>> > by Project 98 to build a plan.
>> >
>> > That wasn't very satisfactory even then as the link code seemed flaky!
>> > (probably my code that is <lol>)
>> >
>> > I need to interface with Project again and still need to use A97 as the
>> > app,
>> > though the version of Project could I guess be anything from P98 
>> > through
>> > to
>> > the latest version.
>> >
>> > Is there any type of tutorial or guidance you guys can offer to get me
>> > started on this path? For example,
>> >
>> > Can I use the A97 Jet 3.51 database to link from a current version of
>> > Project, or could I develop a specific database in, say Jet 4 for
> Project
>> > to
>> > link to, and then use OLEDB to link to it from A97? Does the latest
>> > Project
>> > use VBA as the programming interface?
>> >
>> > Comments Appreciated
>> >
>> > -- 
>> > Kahuna
>> > ------------ 
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>>
>>
>
>

Relevant Pages

  • Re: Using Access 97 with Project
    ... Project 2003 seems to be fine with READING an Access 97 mdb. ... >those table through A97 using an ODBC driver? ... "Earl Lewis" wrote in message ... > wants to create one Access database for every project. ...
    (microsoft.public.access.externaldata)
  • Re: Using Access 97 with Project
    ... "Earl Lewis" wrote in message ... Can the MSP2002 then read the A97 database after its converted? ... Is it possible to keep the Db created with MSP in A2k format and link ...
    (microsoft.public.access.externaldata)
  • Re: Using Access 97 with Project
    ... Can the MSP2002 then read the A97 database after its converted? ... from my A97 app and have them read by MSP. ... I think these are at the heart of my challenge Earl, ...
    (microsoft.public.access.externaldata)
  • Re: Using Access 97 with Project
    ... "Earl Lewis" wrote in message ... an access 97 database though. ... >>those table through A97 using an ODBC driver? ... > You'd only need Access 2000 or greater to conver the initial mdb from A2k ...
    (microsoft.public.access.externaldata)
  • Re: Using Access 97 with Project
    ... Thanks Earl, and I know what you mean. ... my entire architecture is based on A97 and until it's proven otherwise ... If I need to move design strategy it will likely be to another database ...
    (microsoft.public.access.externaldata)
Loading