Quicken on a home network.

Posted by Bill_Phillips on December 10, 2006, 7:04 pm

Please log in for more thread options

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.

Posted by David H. Lipman on December 10, 2006, 7:24 pm

Please log in for more thread options

| 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_AQ_share on PC B; Net Use Q: \PC_AQ_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.

--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm

Posted by BeeL on December 10, 2006, 10:41 pm

Please log in for more thread options

David H. Lipman wrote:

> | 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

> Example: \PC_AQ_share on PC B; Net Use Q: \PC_AQ_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.

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 filesquicken), I
added a text file called "quicken.cmd" which consists of the following 3
lines:

net use q: \dilbertd
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
filesquickenwqw.exe" to "c:program filesquickenquicken.cmd". Also,
I set the start-in location to cprogram filesquicken.

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

Posted by Andrew DeFaria on December 11, 2006, 1:12 am

Please log in for more thread options

This is a multi-part message in MIME format.
--------------030404020902010802040606
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

BeeL wrote:

> David H. Lipman wrote:

>> | 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_AQ_share on PC B; Net Use Q: \PC_AQ_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.

> 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 filesquicken), I

> added a text file called "quicken.cmd" which consists of the following

> 3 lines:

> net use q: \dilbertd

> 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

> filesquickenwqw.exe" to "c:program filesquickenquicken.cmd".

> Also, I set the start-in location to cprogram filesquicken.

> 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.

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 FilesQuickenQw.exe""", 1, true)

' Remove semaphoreFile
fso.DeleteFile (semaphoreFile)
End If

--

Andrew DeFaria <http://defaria.com>
I thought about how mothers feed their babies with little tiny spoons
and forks so I wonder what Chinese mothers use. Toothpicks?

--------------030404020902010802040606
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
BeeL wrote:
<blockquote cite="midJ7OdnfSTGsobTuHYnZ2dnUVZ_s6onZ2d@comcast.com"
type="cite">David H. Lipman wrote:
 
<blockquote type="cite">From: "Bill_Phillips"
<a class="moz-txt-link-rfc2396E"
 
 
| 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_AQ_share   on PC B;  Net Use Q: 
\PC_AQ_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.
 
</blockquote>
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 filesquicken), I
added a text file called "quicken.cmd" which consists of the following
3 lines:
 
 
    net use q: \dilbertd
 
    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
filesquickenwqw.exe" to "c:program filesquickenquicken.cmd". Also,
I set the start-in location to cprogram filesquicken.
 
 
 
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.
 
</blockquote>
Or... create a small vbs script to make a semaphore file to coordinate
access to the Quicken database: 
<blockquote><tt>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 FilesQuickenQw.exe""", 1,
true) 
 
    ' Remove semaphoreFile 
    fso.DeleteFile (semaphoreFile) 
End If 
</tt> 
</blockquote>
<pre>-- </pre>
<a href="http://defaria.com">Andrew DeFaria</a> 
I thought about how mothers feed their
babies with little tiny spoons and forks so I wonder what Chinese
mothers use. Toothpicks?
</body>
</html>

--------------030404020902010802040606--

Posted by Bob Wang on December 10, 2006, 8:09 pm

Please log in for more thread options

https://quicken.custhelp.com/cgi-bin/quicken.cfg/php/enduser/std_adp.php?p_faqid=1725&p_topview=1
Quicken is not designed or tested for use over a network or on a shared
drive. Due to the large variety of possible network configurations, Intuit
will not be able to offer technical assistance for any problems resulting
from use of the Quicken program on a network.

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.

>>>