RE: No data in Backend

Jim,
Thanks for your reply. I guess I wasn't clear about the databases.
These databases are all independent of each other. In other words one client
has nothing to do with the other. The database is installed in the same
folder on all computers and the name of the data file is NOT hard coded for
backup purposes. Each client has their own computer and their data is
totaling independent of anyone elses.
As I stated in my orginal question this problem of no data in the data file
and not being able to locate the data file, ONLY occurs on Window Vista
machines.
Thanks for your input Jim, but the situation you describe does not apply to
my problem.

John G


"Jim Burke in Novi" wrote:

It's possible that the drives are mapped differently on different computers.
If you have the name of the DB hard-coded for backup purposes, this won't
work if different users have drives mapped differently. i.e. if the DB is on
a server'c C drive, it's possible that for some users that drive is actually
mapped as something other than C. That's the only thing I can think of.

As for relinking, you should only re-link tables when you install a new
version of the FE and there are new tables that have been added. Otherwise
there is no need to re-link. In my experience re-linking causes the FE to
grow in size and over time if the FE keeps growing this can cause peformance
problems.

"John G" wrote:

Hi,
I have some clients running Windows Vista and some clients running Windows
XP. My database is developed using MS Access 2003 and is split. Both the FE
and BE reside in the same folder on the same computer. All clients are using
MS Access 2003 runtime. When my database program is opened the tables are
automatically relinked. After the client inputs data he tries to backup the
data (backend) by clicking on a menu item that points to the code to backup
the backend. He gets an error 3024..(can not locate the file.) Upon examining
the data file we discovered that it is empty but the data that he entered is
still showing in the forms. How can this be? This problem only occurs on
machines running Vista. It does not happen on Windows XP machines. When he
closes the database (frontend) and reopens it the data is still showing in
the forms, but the backend data file is empty.
I don't understand how there can be data showing in the forms but none in
the actual data file.
What is Vista doing with the data and why can it not locate the data file?
Anyone have any ideas?
.

Relevant Pages

  • Re: Questions about serving database
    ... recommended a PC over a Mac. ... specs for a computer, and if my client environment is almost all mac, ... I've set up my database with a data file, ...
    (comp.databases.filemaker)
  • Re: Spash screens in a Access 2003 application. How?
    ... I've found that splitting databases can be slower than a non-split database. ... We reuse this screen for Help | About so it can stay on screen for the client when they phone. ... That way you know things like which version of your software they are running, which version of Access, who they are logged in as (useful for logging or determining their permissions), and what data file they are actually connected to. ...
    (comp.databases.ms-access)
  • Re: Access Database becoming corrupt
    ... I supported a client with and access app that had close to a 1GB data file ... and 6-8 concurrent users before they moved to sql. ... Hired vendor to create inventory and sales database in ms-access. ...
    (microsoft.public.windows.server.sbs)
  • Re: Opinions needed about the best "Middleware suite" kbmMW vs. RODA
    ... kbmMW supports cross db in such way that all you need to do in your application is to set one property to switch to ... What one have to concentrate about is minimizing the amount of data moved from the app server to the client. ... C/S setup's usually have a quite active chatter going on between the client and the database, ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Access 2003 Macro Security Modification
    ... the desired way to prevent the macro security warning is to ... digitally sign your database. ... Your database fileon the client computer. ...
    (microsoft.public.access.modulesdaovba)