Re: Use of an Access 97 database by XP and 97 users

From: Chris Mills (phad_nospam_at_cleardotnet.nz)
Date: 07/28/04 

Date: Wed, 28 Jul 2004 17:06:46 +1200

If you are rolling it out with VB code, why is the Access version relevant?

Do you mean they are using both MS-Access and a VB-code front-end.

If they are opening it in VB code, why mention opening it in Access?
Conversely, why mention VB code?

An A97 "BE" can be rolled out with any later version. Of course, only
MS-Access97 can repair/compact it (I understand).

To suppress the later-version question whether to upgrade, I thought this was
suppressed AFTER the FIRST time you so open the database. But that is too
easy, you must be asking something else...

(I take splitting into FE/BE as a given, since you mentioned "together with VB
code". However, even if it was a single database/code, I thought it would
suppress the message after the first "proper running". There is no flag/since
it's automatic if done right)

Chris

"justin" <anonymous@discussions.microsoft.com> wrote in message
news:4ce101c473c4$ade951f0$a301280a@phx.gbl...
> Hi, I have encountered a problem with running a multi-
> user Access 97 database, and hope someone out there has
> the answer. Please help...
>
> I am rolling out a database (together with VB code) to 15
> users, some of whom have Access 97, some of whom have
> Access XP. To be used by the '97 users, I have to roll it
> out as an Access 97 database.
>
> My problem is that whenever XP users open the database,
> they are asked if they want to upgrade it to XP.
> Occasionally users reply YES, the database is converted
> to XP, and is then no longer usable by '97 users.
>
> What I am looking for is an option / flag which in XP
> would switch off the option to upgrade. Does anyone have
> the answer, or a suggestion as to how else this prblem
> might be overcome?
>
> Many thanks in advance,
>
> Justin
>

Relevant Pages

  • Re: access family medical claims database
    ... "Looking for a database for keeping family medical claim records. ... I'm not even sure if an Access frontend would pass HIPAA ... PS Albert, sometimes you say 'ms-access', other times you say ... Sometimes you say 'JET', ...
    (microsoft.public.access.gettingstarted)
  • Re: To Normalize or not ??
    ... The problem is that when you run a split database, ... save a word document (it is in memory, and thus does not get saved). ... ms-access is different then excel or word. ... database server. ...
    (microsoft.public.access.formscoding)
  • Re: forms vs. DAP
    ... form in the northwind database. ... was to me but they are more sensitive to the executives ... using a WAN with ms-access answered the mystery of why I ... a way to launch ms-access without violating any security. ...
    (microsoft.public.access.forms)
  • Re: Porting Access applications to the web. ASP or PHP?
    ... Using PHP with ms-access database, or mysql database makes no difference. ... If you just need some applications to be used by tele-commute employees, ... If you want a nice rich "forms" like development system for the web, ...
    (microsoft.public.access.formscoding)
  • Re: Point of Sale Terminals
    ... MS-Access is as suitable as any database product for a given application (in ... this case POS). ... All of the issues are standard issues for any database or subject. ... It's a nuisance changing hardware brands, ...
    (microsoft.public.access.developers.toolkitode)
Quantcast