I have a home network, three machines. All XP Service Pack 2. I'd like to be able to access the check register from any of the machines, but so far I haven't been able to make anything work. If anybody is doing it this way I'd sure like some advise.
Thanks.
From: "Bill_Phillips"
| I have a home network, three machines. All XP Service Pack 2. I'd like to | be able to access the check register from any of the machines, but so far I | haven't been able to make anything work. If anybody is doing it this way | I'd sure like some advise. | | Thanks. |
File and Print Service must be enabled on the PC going to share the Quicken data.
You have to 'share' the data files in a NT Share.
The users on PC A and PC B must have the same Account Name and Password.
If PC A is sharing the files, you should map a drive letter to the share on PC B
Example: \\PC_A\Q_share on PC B; Net Use Q: \\PC_A\Q_share
On PC B use drive "Q:" to access the data files. Only ONE computer can access the Quicken data files at any given time.
For optimal results when using Quicken, Intuit recommends installing a separate version of Quicken on each computer's hard drive. To purchase additional copies of the current version of Quicken please visit Quicken.com.
Note: The QuickBooks family of products helps you power your small business. This family of products does offer multiple user packages for use in combination with a network.
Thanks.
From: "Bob Wang"
|
I have been sharing Quicken data files over my SOHO LAN for years.
Quicken DOS [v8.0] and Quicken 2006. No problems to date !
Ever hear of standards? SMB is a standard. It really doesn't matter what network configuration is used - it's still an SMB packet following SMB protocol.
Standard disclaimer.
So are operating systems. They seem to handle networks relatively OK.
Agreed, Quicken is not designed for concurrent access, though it could be.
Optimal results? Well yes loading a program from the network is slower than loading it locally. But it's not that much slower. Hell I share all my videos and audio files from a share (a SMB share on my Linux box actually) with no problems or notice of latency. The real problem is that the remotely loaded Quicken will search the local registry and not find what it expects.
Of course. Can you say Ka-ching? I knew you could!
Thus proving that it can indeed be done...
Additionally, Intuit does not recommend the use of your Quicken data files over a network due to the increased likelihood that data corruption will occur. Quicken is designed to save the data incrementally as it is entered. For this reason, network instability or the use of a data file by multiple people at the same time will often lead to data integrity issues.
For optimal results when using Quicken, Intuit recommends installing a separate version of Quicken on each computer's hard drive. To purchase additional copies of the current version of Quicken please visit Quicken.com.
Note: The QuickBooks family of products helps you power your small business. This family of products does offer multiple user packages for use in
Additionally, Intuit does not recommend the use of your Quicken data files over a network due to the increased likelihood that data corruption will occur. Quicken is designed to save the data incrementally as it is entered. For this reason, network instability or the use of a data file by multiple people at the same time will often lead to data integrity issues.
For optimal results when using Quicken, Intuit recommends installing a separate version of Quicken on each computer's hard drive. To purchase additional copies of the current version of Quicken please visit Quicken.com.
Note: The QuickBooks family of products helps you power your small business. This family of products does offer multiple user packages for use in combination with a network.
We've been using Quicken on our server-based home network for years now .. no problems with data corruption or access from workstations.
I'm sure that major corporations everywhere would be surprised to hear what chances they're taking with their data by networking it.
the Quicken
My findings agree with David Lipman's. Here is how I do it ...
On machine A I have quicken installed, and my data files reside on this machine.
On machine B, I have quicken installed. I did these two things:
1: In the directory where quicken lives (c:\program files\quicken), I added a text file called "quicken.cmd" which consists of the following 3 lines:net use q: \\dilbert\d start qw.exe exit
(note: Change the first line to refer to the relevant location on machine A. In my house the quicken data is on the d-drive of a machine named dilbert.)
2: I edited the shortcut to quicken so that it will execute the cmd file. That is, I right-clicked on the quicken desktop icon, edited its properties, and changed the target from "c:\program files\quickenw\qw.exe" to "c:\program files\quicken\quicken.cmd". Also, I set the start-in location to c\program files\quicken.As David says, you need to be careful not to have 2 machines running quicken at the same time. Also, Machine A has to be sharing its files.
Good luck
-- BeeL
I'm no lawyer, but my reading of this is that if you run Quicken over a network, you need to purchase separate licenses for each computer.
Good thing I'm NOT a lawyer.
The license agreement for Quicken 2007 Home & Business allows for use on "up to three (3) computers used by a single household."
I'm no lawyer, but my reading of this is that if you run Quicken over a network, you need to purchase separate licenses for each computer.
Or... create a small vbs script to make a semaphore file to coordinate access to the Quicken database:
On Error Resume Next
Set WshShell = WScript.CreateObject ("WScript.Shell") Set fso = CreateObject ("Scripting.FileSystemObject")
Set Env = WshShell.Environment ("USER")
semaphoreFile = Env ("TMP") & "\quicken_in_use"
' Check to see if Quicken is in use If fso.FileExists (semaphoreFile) Then WScript.Echo "Somebody's using Quicken" Else ' Create semaphore file Set File = fso.CreateTextFile (semaphoreFile) File.Close
' Start Quicken i = WshShell.Run ("""C:\Program Files\Quicken\Qw.exe""", 1, true)
' Remove semaphoreFile fso.DeleteFile (semaphoreFile) End If
The license agreement for Quicken 2007 Home & Business allows for use on "up to three (3) computers used by a single household."
I'm no lawyer, but my reading of this is that if you run Quicken over a network, you need to purchase separate licenses for each computer. =====================================Many companies will let you use one copy on your desktop *and* your laptop (assuming you're using your laptop when you can't use your desktop PC). Some will let you have them on more than one desktop PC as long as there isn't "concurrent" use (which I suspect wouldn't work with Quicken anyway). Licensing agreements are all over the place on this. Deb
I use a nice program to help with the networking aspects: Network Magic.
I just share the folder that the data files reside in on the 'main' machine and access it through the other two machines.
I have loaded the Quicken Program on each machine and performed the updates to get the programs all at the same level.
Good luck.
john
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.