PC Review


Reply
 
 
=?Utf-8?B?TWF4?=
Guest
Posts: n/a
 
      26th Jan 2006
If we have our database in Access 97 with many users connecting to the data
from their own "front ends", can one of us upgrade to Access XP? If so, can
that XP user upgrade only their own "front end" or the data as well? Can the
97 users link to XP data? (This I think is No) Can the XP user link to 97
data? (This last I think is Yes)

Thanks in advance.
 
Reply With Quote
 
 
 
 
Chriske911
Guest
Posts: n/a
 
      26th Jan 2006
> If we have our database in Access 97 with many users connecting to the data
> from their own "front ends", can one of us upgrade to Access XP? If so, can
> that XP user upgrade only their own "front end" or the data as well? Can the
> 97 users link to XP data? (This I think is No) Can the XP user link to 97
> data? (This last I think is Yes)
>
> Thanks in advance.


keep the back end database in the office 97 format
upgrade the front database to office XP
no troubles for anyone changing data from either front

there is actually no other combination possible

grtz


 
Reply With Quote
 
Allen Browne
Guest
Posts: n/a
 
      26th Jan 2006
You can have different versions of Access running on different machines,
sharing the same data.

The front end should ideally be an MDE in the right version of Access for
the user.

The back end must be the oldest version in use, since it is a shared file,
and the A97 users cannot access the mdb if it is a later version.

In practice, this all works quite well. The A2002 users find it a little
slower than the A97 users, because the JET 4 calls have to be converted to
JET 3.5.

There are a couple of quirks to avoid. Make sure the A2002 users have
unchecked the box:
Tools | Options | Advanced | Open databases using record-level locking.
A97 does not support record-level locking (and it is a performance issue
anyway) so there is absolutely no point in enabling it when the back end is
an A97 mdb. If you don't uncheck the box, you may find that some operations
don't work. (Particularly, complex operations wrapped in a DAO transaction.)

The other issue is a performance one, where the SubdatasheetName property is
an issue. Normally you can set this property to [None], but since the
attached A97 tables don't have this property, trying to set it has no
effect. The workaround is to actually CreateProperty() on the A97 tables. It
is dbText type, and the value is the string "[None]". Once you create the
property that A2002 expects, it understands the setting, and so this
performance issue disappears. The basic idea is:
Currentdb.TableDefs("MyTable").CreateProperty("SubdatasheetName",
dbText, "[None]")

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Max" <(E-Mail Removed)> wrote in message
news:633D035B-833C-4AA4-BD4D-(E-Mail Removed)...
> If we have our database in Access 97 with many users connecting to the
> data
> from their own "front ends", can one of us upgrade to Access XP? If so,
> can
> that XP user upgrade only their own "front end" or the data as well? Can
> the
> 97 users link to XP data? (This I think is No) Can the XP user link to 97
> data? (This last I think is Yes)
>
> Thanks in advance.



 
Reply With Quote
 
=?Utf-8?B?TWF4?=
Guest
Posts: n/a
 
      26th Jan 2006
Thanks both for the prompt replies.

"Chriske911" wrote:

> > If we have our database in Access 97 with many users connecting to the data
> > from their own "front ends", can one of us upgrade to Access XP? If so, can
> > that XP user upgrade only their own "front end" or the data as well? Can the
> > 97 users link to XP data? (This I think is No) Can the XP user link to 97
> > data? (This last I think is Yes)
> >
> > Thanks in advance.

>
> keep the back end database in the office 97 format
> upgrade the front database to office XP
> no troubles for anyone changing data from either front
>
> there is actually no other combination possible
>
> grtz
>
>
>

 
Reply With Quote
 
=?Utf-8?B?TWF4?=
Guest
Posts: n/a
 
      26th Jan 2006
Thanks both for the prompt replies.

"Allen Browne" wrote:

> You can have different versions of Access running on different machines,
> sharing the same data.
>
> The front end should ideally be an MDE in the right version of Access for
> the user.
>
> The back end must be the oldest version in use, since it is a shared file,
> and the A97 users cannot access the mdb if it is a later version.
>
> In practice, this all works quite well. The A2002 users find it a little
> slower than the A97 users, because the JET 4 calls have to be converted to
> JET 3.5.
>
> There are a couple of quirks to avoid. Make sure the A2002 users have
> unchecked the box:
> Tools | Options | Advanced | Open databases using record-level locking.
> A97 does not support record-level locking (and it is a performance issue
> anyway) so there is absolutely no point in enabling it when the back end is
> an A97 mdb. If you don't uncheck the box, you may find that some operations
> don't work. (Particularly, complex operations wrapped in a DAO transaction.)
>
> The other issue is a performance one, where the SubdatasheetName property is
> an issue. Normally you can set this property to [None], but since the
> attached A97 tables don't have this property, trying to set it has no
> effect. The workaround is to actually CreateProperty() on the A97 tables. It
> is dbText type, and the value is the string "[None]". Once you create the
> property that A2002 expects, it understands the setting, and so this
> performance issue disappears. The basic idea is:
> Currentdb.TableDefs("MyTable").CreateProperty("SubdatasheetName",
> dbText, "[None]")
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Max" <(E-Mail Removed)> wrote in message
> news:633D035B-833C-4AA4-BD4D-(E-Mail Removed)...
> > If we have our database in Access 97 with many users connecting to the
> > data
> > from their own "front ends", can one of us upgrade to Access XP? If so,
> > can
> > that XP user upgrade only their own "front end" or the data as well? Can
> > the
> > 97 users link to XP data? (This I think is No) Can the XP user link to 97
> > data? (This last I think is Yes)
> >
> > Thanks in advance.

>
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off



Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 05:07 PM.