RE: Error 3085 Format$ being changed to [Format$] in query by one



Dale, Sorry It took a while to get back to your questions. I tried twice
yesterday to post and got errors connecting to the server site. So I will see
if this works today.
We are single-user database. I wish only one person to be updating/using
the database. That person has a backup person that takes over on days that
the first person is sick/vacation. Of course the backup person would like to
use their own computer to get into the database. Yes, the database is on the
network drive. The Boss wanted it there so the Network daily backup would
cover backing up the database each night. I have tried to set each person
that might go into the database to go in for Exclusive rights. This is our
first database. Centralized or Distributed? That is a good question. The Boss
picked Centralized. I have to go the way of the person that signs the
paycheck (though I did mention my concerns). For a small shop with no I.T.
staff and one user and one backup user, I hope the centralized (one copy of
the database on the Network server drive) will be a safe starting point.

If you have a link to where these Rules are posted, I would be very happy
to see them. Thanks for your concern and input,
Steve
--
Thanks for your Help and Patience.


"Dale Fye" wrote:

Steve,

When you say it "works great from two different machines" do you mean that
the application is sitting on a server or one of the individual machines, and
you are running that mdb over the network, or do you mean that each computer
has a copy of the frontend (forms, queries, reports) and the backend (data)
is on a networked computer?

If you are working in a multi-user environment, you should:

1. Always split your database into a frontend (put a copy on each users
machine) and a backend (data stored on a server or file sharing machine).
Link the data tables from the backend to the frontend

2. Never allow the users to use a instance of the frontend that is actually
loaded on the network. They should always have to use the copy that is on
their desktop or on their hard drive.

It sounds like you have violated both of these rules. Clean up the file,
run the database splitter (Tools->Database Utilities -> Database splitter) to
separate the front end from the backend. Then copy the front end to each of
the individual users computers. Open the mdb in design view on each computer
and make sure that the references are all there. Try again.

HTH
Dale

--
Email address is not valid.
Please reply to newsgroup only.


"Steven Chicago,Illinois" wrote:

I have a report that is query driven. It works great from two different
computers. A third user tries to run it and mysteriously the query changes
and she receives Error 3085. Then if I or another user tries from our
machines, we get the error too. I have figured out that something is changing
the :"Session Date By Day: Format$([Asshanrpt Work Table].[Session
Date],'Short Date')" statement to:
"Session Date By Day: [Format$]([Asshanrpt Work Table].[Session
Date],'Short Date')". The change from Format$ to [Format$] ? Why? I fix the
query and the report runs fine on all machines (but her's), until she gets on
the database and tries to run the report again. We are using Access2002-2003
on Windows XP (on our machines) with the database out on our network server
drive. This is where I wish there was a way to LOCK a query/report/etc so no
user or? could change the code. Anybody come across the same problem?

I have searched the discussion group history and seen this error mentioned,
but not in the way it is effecting us. I am also a little confused as to if I
should have put this question in the General area or queries or another area?

--
Thanks for your Help and Patience.
.



Relevant Pages

  • Performance optimization vs satisficing (was Language Oriented Programming)
    ... >machines that were too small. ... Microsoft has been a leading offender here. ... >arcane issue for server engines. ... magnitude slower, yes, I recall working on a 200mb database, trying to ...
    (comp.object)
  • Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
    ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote data entry solution needed for Access 2007
    ... Users open the database remotely and use its forms to enter data. ... Why it doesn't work: network lag time. ... our network admin says our Citrix server is 2000 and ... HTML-based form working with an ASP file to send data to the database. ...
    (microsoft.public.access.externaldata)
  • Re: Vista, SBS 2003 and RAS not working
    ... We have a windows SBS 2003 server – straight out of the box, ... The VPN connection between your computer and the VPN server could not ... You mention that the clients are Vista machines, which means that their built-in firewall works on outgoing messages as well as incoming ones, and the firewall needs to be told that outgoing PPTP VPN connections should be allowed. ... Computers don't need to be joined to the domain to connect by VPN, by the way, so you can use other remote computers for testing, it's just that only domain machines get access to all network resources easily. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.windowsxp.network_web)

Loading