salv utility is causing problems in my data file

I am having a problem with Money 2004 and the built in file
maintenance utilities.

When I upgraded my data file from 2003 to 2004, I had a problem that
my new converted file contained some accounts that wouldn't reconcile
any longer. What I mean by that is that some transactions in the
register simply couldn't selected. When you clicked on the
transaction in the reconciliation window, Money would not change to an
arrow. So the account won't reconcile.

Money tries fix the reconcile error and "sees" the transaction that
would fix the problem. But when Money tries to fix it, an error
"Internal Program Error" pops up.

Microsoft tech support says "file corruption" so I start over with a
new file.

So, I started with a completely new 2004 file 6 months ago. The file
is acting fine. Today, I decided to use the file maintenance utility
(Level 1 and then Level 2) which I thought were preventative utilities
(like a Scandisk). Level 2 told me there were a few problems that it
fixed.

Now when I try to reconcile, I get the same error as above.

I've gone back to my 6 month old file, pre salv, and it works fine.

If I didn't know better, I'd say that the file maintenance utility is
making things worse for me; twice in six months.

Thoughts?

via_newsgroup
Wed Dec 10 13:01:55 CST 2003

In microsoft.public.money, JAC wrote:

>
>If I didn't know better, I'd say that the file maintenance utility is
>making things worse for me; twice in six months.
>
>Thoughts?

I am sorry to hear of your problems.

Are you using the version of salv.exe dated 06/18/03 from your
install? It is newer than the one you can download.

Have you tried both Level 1 and Level 2? Try more than one time with
different levels in sequence.

It would be good if you had more backups to choose from. Once or
twice per month seems about right to change backup file names so you
do not overwrite too much.

Arge
Wed Dec 10 17:13:01 CST 2003

Hi JAC

I have noticed the exact same thing. Slav.exe corrects the problems but you
can no longer do anything with it. In order to get around this I have found
that if I delete the transaction and then re-enter it, it will then allow me
to reconcile it. I have also noticed that it continually happens to me on 3
different transactions which are all transfers from one account to another.
All three of the transactions are scheduled bills and it continually happens
to these three transactions monthly only. Each of the transactions are also
on-line MSN Bill Pay transactions. I have tried several different things
but the problem continues to happen, so I have finally deleted all three as
scheduled transactions to see if that is related.

I do know that after I delete them and re-enter them, the problem is gone
and everything seems to be back to normal. I will not know if deleting them
as scheduled transactions will help until next month.

Bob
"JAC" <techguy71-at-mchsi-dot-com@> wrote in message
news:j2qetvkii0cdd4gq4iiicrd4j8ivat72fj@4ax.com...
> I am having a problem with Money 2004 and the built in file
> maintenance utilities.
>
> When I upgraded my data file from 2003 to 2004, I had a problem that
> my new converted file contained some accounts that wouldn't reconcile
> any longer. What I mean by that is that some transactions in the
> register simply couldn't selected. When you clicked on the
> transaction in the reconciliation window, Money would not change to an
> arrow. So the account won't reconcile.
>
> Money tries fix the reconcile error and "sees" the transaction that
> would fix the problem. But when Money tries to fix it, an error
> "Internal Program Error" pops up.
>
> Microsoft tech support says "file corruption" so I start over with a
> new file.
>
> So, I started with a completely new 2004 file 6 months ago. The file
> is acting fine. Today, I decided to use the file maintenance utility
> (Level 1 and then Level 2) which I thought were preventative utilities
> (like a Scandisk). Level 2 told me there were a few problems that it
> fixed.
>
> Now when I try to reconcile, I get the same error as above.
>
> I've gone back to my 6 month old file, pre salv, and it works fine.
>
> If I didn't know better, I'd say that the file maintenance utility is
> making things worse for me; twice in six months.
>
> Thoughts?

JAC
Thu Dec 11 08:40:31 CST 2003

I am using whatever is built into the File menu of Money 2004.

I back up every day with a different backup name. That doesn't help
me with the issue of why a 6 month old file is telling me there are
errors in it and the file maintenance utilities "fix" it by not
letting me reconcile anymore.

On Wed, 10 Dec 2003 19:01:55 GMT, via_newsgroup@please.tnx(Cal
Learner-- MVP) wrote:

>In microsoft.public.money, JAC wrote:
>
>>
>>If I didn't know better, I'd say that the file maintenance utility is
>>making things worse for me; twice in six months.
>>
>>Thoughts?
>
>I am sorry to hear of your problems.
>
>Are you using the version of salv.exe dated 06/18/03 from your
>install? It is newer than the one you can download.
>
>Have you tried both Level 1 and Level 2? Try more than one time with
>different levels in sequence.
>
>It would be good if you had more backups to choose from. Once or
>twice per month seems about right to change backup file names so you
>do not overwrite too much.
>

JAC
Thu Dec 11 08:40:31 CST 2003

I agree. It is happening on scheduled transaction that are transfers
(i.e., payment to other accounts).

Sounds like we have a trend here (at least a trend of 2). That is
better than where I was before!

On Wed, 10 Dec 2003 18:13:01 -0500, "Arge"
<bigbc37(nospam)@hotmail.com> wrote:

>Hi JAC
>
>I have noticed the exact same thing. Slav.exe corrects the problems but you
>can no longer do anything with it. In order to get around this I have found
>that if I delete the transaction and then re-enter it, it will then allow me
>to reconcile it. I have also noticed that it continually happens to me on 3
>different transactions which are all transfers from one account to another.
>All three of the transactions are scheduled bills and it continually happens
>to these three transactions monthly only. Each of the transactions are also
>on-line MSN Bill Pay transactions. I have tried several different things
>but the problem continues to happen, so I have finally deleted all three as
>scheduled transactions to see if that is related.
>
>I do know that after I delete them and re-enter them, the problem is gone
>and everything seems to be back to normal. I will not know if deleting them
>as scheduled transactions will help until next month.
>
>Bob
>"JAC" <techguy71-at-mchsi-dot-com@> wrote in message
>news:j2qetvkii0cdd4gq4iiicrd4j8ivat72fj@4ax.com...
>> I am having a problem with Money 2004 and the built in file
>> maintenance utilities.
>>
>> When I upgraded my data file from 2003 to 2004, I had a problem that
>> my new converted file contained some accounts that wouldn't reconcile
>> any longer. What I mean by that is that some transactions in the
>> register simply couldn't selected. When you clicked on the
>> transaction in the reconciliation window, Money would not change to an
>> arrow. So the account won't reconcile.
>>
>> Money tries fix the reconcile error and "sees" the transaction that
>> would fix the problem. But when Money tries to fix it, an error
>> "Internal Program Error" pops up.
>>
>> Microsoft tech support says "file corruption" so I start over with a
>> new file.
>>
>> So, I started with a completely new 2004 file 6 months ago. The file
>> is acting fine. Today, I decided to use the file maintenance utility
>> (Level 1 and then Level 2) which I thought were preventative utilities
>> (like a Scandisk). Level 2 told me there were a few problems that it
>> fixed.
>>
>> Now when I try to reconcile, I get the same error as above.
>>
>> I've gone back to my 6 month old file, pre salv, and it works fine.
>>
>> If I didn't know better, I'd say that the file maintenance utility is
>> making things worse for me; twice in six months.
>>
>> Thoughts?
>

via_newsgroup
Thu Dec 11 08:52:16 CST 2003

In microsoft.public.money, JAC wrote:

>I am using whatever is built into the File menu of Money 2004.
>
>I back up every day with a different backup name. That doesn't help
>me with the issue of why a 6 month old file is telling me there are
>errors in it and the file maintenance utilities "fix" it by not
>letting me reconcile anymore.

Microsoft might be able to help you out. I would contact them
directly.

Arge
Thu Dec 11 10:17:45 CST 2003

JAC

Let me know if deleting them and then re-entering the transactions allows
you to reconcile it. Delete it from the originating account.

Bob
"JAC" <techguy71-at-mchsi-dot-com@> wrote in message
news:8lvgtvsq2cakgsge19rac290eirvc7d477@4ax.com...
> I agree. It is happening on scheduled transaction that are transfers
> (i.e., payment to other accounts).
>
> Sounds like we have a trend here (at least a trend of 2). That is
> better than where I was before!
>
> On Wed, 10 Dec 2003 18:13:01 -0500, "Arge"
> <bigbc37(nospam)@hotmail.com> wrote:
>
> >Hi JAC
> >
> >I have noticed the exact same thing. Slav.exe corrects the problems but
you
> >can no longer do anything with it. In order to get around this I have
found
> >that if I delete the transaction and then re-enter it, it will then allow
me
> >to reconcile it. I have also noticed that it continually happens to me
on 3
> >different transactions which are all transfers from one account to
another.
> >All three of the transactions are scheduled bills and it continually
happens
> >to these three transactions monthly only. Each of the transactions are
also
> >on-line MSN Bill Pay transactions. I have tried several different things
> >but the problem continues to happen, so I have finally deleted all three
as
> >scheduled transactions to see if that is related.
> >
> >I do know that after I delete them and re-enter them, the problem is gone
> >and everything seems to be back to normal. I will not know if deleting
them
> >as scheduled transactions will help until next month.
> >
> >Bob
> >"JAC" <techguy71-at-mchsi-dot-com@> wrote in message
> >news:j2qetvkii0cdd4gq4iiicrd4j8ivat72fj@4ax.com...
> >> I am having a problem with Money 2004 and the built in file
> >> maintenance utilities.
> >>
> >> When I upgraded my data file from 2003 to 2004, I had a problem that
> >> my new converted file contained some accounts that wouldn't reconcile
> >> any longer. What I mean by that is that some transactions in the
> >> register simply couldn't selected. When you clicked on the
> >> transaction in the reconciliation window, Money would not change to an
> >> arrow. So the account won't reconcile.
> >>
> >> Money tries fix the reconcile error and "sees" the transaction that
> >> would fix the problem. But when Money tries to fix it, an error
> >> "Internal Program Error" pops up.
> >>
> >> Microsoft tech support says "file corruption" so I start over with a
> >> new file.
> >>
> >> So, I started with a completely new 2004 file 6 months ago. The file
> >> is acting fine. Today, I decided to use the file maintenance utility
> >> (Level 1 and then Level 2) which I thought were preventative utilities
> >> (like a Scandisk). Level 2 told me there were a few problems that it
> >> fixed.
> >>
> >> Now when I try to reconcile, I get the same error as above.
> >>
> >> I've gone back to my 6 month old file, pre salv, and it works fine.
> >>
> >> If I didn't know better, I'd say that the file maintenance utility is
> >> making things worse for me; twice in six months.
> >>
> >> Thoughts?
> >
>

JAC
Thu Dec 11 13:25:41 CST 2003

I am doing so right now. So far I get the "must be some file
inconsistencies. Have you tried to export/import into a new file?"

That answer is fine once. Not twice in 6 months.

On Thu, 11 Dec 2003 14:52:16 GMT, via_newsgroup@please.tnx(Cal
Learner-- MVP) wrote:

>In microsoft.public.money, JAC wrote:
>
>>I am using whatever is built into the File menu of Money 2004.
>>
>>I back up every day with a different backup name. That doesn't help
>>me with the issue of why a 6 month old file is telling me there are
>>errors in it and the file maintenance utilities "fix" it by not
>>letting me reconcile anymore.
>
>Microsoft might be able to help you out. I would contact them
>directly.