Make application run on network computer not on local computer
The formprints out to the network printer beside this network computer, and this would give the person an audible signal that the form is printed and ready to be looked at.
Thank you for taking the time to report an issue.
What's wrong... Please write below.
The code works just fine when I log in and run the the scheduler and has been running correctly for month's on my local computer.
The problem seems to be that when I try to run on a scheduler in Windows 7 there are no network connections.
Anytime I try to connect to a folder on the network the procedure fails when running on the Windows Scheduler.
Dim appAccess As Access.Application
' Create instance of Access Application object. Set appAccess = CreateObject("Access.Application")
' Open WizCode database in Microsoft Access window.
appAccess.OpenCurrentDatabase "B:\Documents and Settings\bconner\Desktop\Template Month End Reports v1.2.mdb", False
' Run Sub procedure.
appAccess.Run "MonthEndReports" Set appAccess = Nothing
However I have other uses that must use the db that can not access the network.
1. split the db
a. Main be on the network
b. Make multi copies of fe for all the others including off network. 2. Make replica for the off network db from the be on the network drive.
3. Copy to offsite computer and Re link the off network db with the replica | db.
4. Copy the replicas to the network drive daily and synchronize with the be on the network. (our network is to slow to work online)
The problem is one of the computers on the network has read-only access to the frontend mdb file whereas a different computer on the network as well as the host computer have full access to the database.
At first I thought the problem was read/write permissions for the computer on this network drive, but that is not the issue. I can add/delete/modify files on the drive from this computer.
Well.by the time I change a couple records from the VISTA machine, the database gets corrupted somehow.
I then have to go in to access and compress and repair the database. This will then work on the other computers, until I go use the VISTA computer again. I can't figure it out for the life of me.
1. Has something changed with VISTA and JET support?
2. Could there be a network issue with VISTA that is crashing the data?
If I logon to the local PC with Administrator rights the program works fine. If I logon on to the local machine with “Power User” rights – it fails. I have given myself Administrator rights while logged on to the network – fails.
I have removed runtime as a factor but it doesn't’t matter. I have tried everything I can think of with Trusted Documents – it doesn't’t matter. Nothing I have tried with Trusted Documents seems to fix the problem.
For eg: 'A' is a computer which has both the Application Software and the Access database.
'B' is a Computer with only Application Software.
'C' is a Computer with only Application Software.
Any insert, update,delete done on the System 'B' & 'C' Must affect the actual database in Computer 'A
So far I have gotten two different error messages. First I get a "Unknown function 'Date' in validation expression or default value on 'tblACHFiles.DateEntered'." Then later I get another error message that says "Execution of this application has stopped due to a run-time error.
The application can't continue and will be shut down." The part that stumps me is that it works on two computers.
At first I thought that there was something on my computer that allowed me to make it work so I installed it on another computer and it worked.
One interesting note is that the two computers that I have gotten it to work on are in a workgroup while the computers that it doesn't work on are part of the network domain.
The back-end of the database is stored on a server in the domain. I checked the permissions on the folder containing the BE and it gives Read/Write/Execute/Modify permissions to everyone involved.
We use a frontend to backend connection. each copy of the frontend is held on each users local computer (in the D: drive), and has linked tables pointing to a folder on a file server(nothing special, just a normal server for holding documents).
We do have 60 users adding and amending records. At times (such as logging out time) the database grinds to a halt due to network traffic (as the users computers are restricted by the server being held up).
If the backend files are made local (as I often do when developing) the speed is massively increased.
Rather than link to the server for the backend, the key tables (the ones doing most of the adding and amending of records) are duplicated on each local computer. When the user loads theprogram in the morning, all tables are updated.