Re: MS ACCESS 2003
On Aug 1, 5:37 pm, "Jeff Pitsch" <j...@jeffpitschconsulting.com>
wrote:
> Are you saying you installed the app while the user was on or you tried
> updating the MDB while the user was on? If the latter, then yes all users
> would have to be off for the MDB to be updated. well, not using the
> application using the MDB.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> "merlin2049er" <merlin204...@discussions.microsoft.com> wrote in message
>
> news:81880222-3266-4424-A10F-E748234DAC74@microsoft.com...
>
>
>
>
>
> > "Jeff Pitsch" wrote:
>
> >> If all your updating is the MDB, then you should be fine
> >> dragging/dropping
> >> it as long as no users are using it of course 
>
> >> Jeff Pitsch
> >> Microsoft MVP - Terminal Services
>
> >> "merlin2049er" <merlin204...@discussions.microsoft.com> wrote in message
> >>news:BF5D43D1-70CB-4B01-BF15-539486C55D01@microsoft.com...
> >> > Hi,
>
> >> > Just wanted to know the correct way to update an .mdb file on the
> >> > terminal
> >> > server?
>
> >> > Is it ok to just drag and drop the file in the same location of the old
> >> > file
> >> > (overwritting it) ?
>
> >> > The db program was installed thru the control panel / add remove
> >> > programs.
>
> >> > Thanks,
> >> > JG
>
> > Thanks.
>
> > I thought that was the correct way of updating the db on the terminal
> > server.
>
> > One other thing. I've installed an accounting package that also uses the
> > runtime version of access 2003, and when I ran this app in the terminal
> > server it said that the .mdb file was in use.
>
> > Not sure why that happened, but I do know at least one user was also using
> > the accounting software remotely.
>
> > Any suggestions?
> > JG- Hide quoted text -
>
> - Show quoted text -
I've found the easiest thing to do is to open Terminal Services
Manager and logoff all sessions that are disconnected. Then if
someone is still active send them a message saying to logoff. After
that I make sure all sessions are logged off from the TSM. I run this
batch file and change the logons to disabled:
@echo off
cls
title Enable, Disable, Query Logins for Terminal Server
color 0E
Rem change logon /query
Rem change logon /disable
Rem change logon /enable
:CHOICE
echo.
echo.
echo.
Echo What would you like to do?
echo.
Echo 1. Disable Logons to the Term Server?
Echo 2. Enable Logons to the Term Server?
Echo 3. See if Logons are enabled?
Echo 4. Exit this program
echo.
echo.
Choice /C:1234
IF errorlevel 4 goto EOF
IF errorlevel 3 goto QUERY
IF errorlevel 2 goto ENABLED
IF errorlevel 1 goto DISABLED
:QUERY
Echo ************* Term Server Status ****************
echo.
change logon /query
echo.
echo.
Pause
GOTO CHOICE
:ENABLED
Echo ************* Term Server Logons Enabled *********
echo.
change logon /enable
echo.
echo.
pause
GOTO CHOICE
ISABLED
Echo ************* Term Server Logons Disabled *********
echo.
change logon /disable
echo.
echo.
pause
GOTO CHOICE
:EOF
You'll now be able to update any .mdb or application for that matter
without being disturbed. Make double sure you have change the setting
back to ENABLED before you logout. This could cause MANY problems for
you if you don't.
Regards,
Matt