SageForum for UK versions of Sage 50- Help and support.

I suggest you try it.

see viewtopic.php?t=49

Have you re-indexed and compressed the files ?

Please do the following basic procedures before posting.

1/ Backup your data (Do not overwrite an old backup that you might later need, make a nice fresh clean one)

2/ Check your data for errors in File>Maintenance.

3/ Re-Index and compress your files in File>Maintenance.

4/ Get the latest ...

I assume everything is fine apart form the warnings?

Have you rebuilt the indexes and compressed the files?

Have you tried running fix again, sometimes things took two runs to get fixed.


If all else fails, I could look at it for you on a "no fix - no fee" basis.


Bruce
http://www.makingithappen ...

Sorry, I think I just got an idea...

Sage Didn't like UNC naming in early versions.

Uninstall the client first

Map the network share to say Drive S: and then re do your network install from the mapped drive letter...

I assume it runs fine on the server...?

First stop check for data corruption
File>Maintenance>Check Data

Second stop Do a TB and check that balances

Third stop, check your CoA (Chart of Accounts) for errors
Nominal>COA>(select)-Edit>Check

Come back here if you still can't resolve it...

Bruce
http://www.makingithappen.co.uk/support.htm

Deleting the file \\server\c\line50\accdata\queue.dta should fix the issue.

Backup first. Or better still backup and rename the file so you can get it back.

Note: Version 5.02 is VERY old, you might like to upgrade the current version is 12!

http://sage.support.makingithappen.co.uk/sales.htm

None are needed for sage to work

I can't remember the version that this was an issue with, but I am pretty sure a service pack was issued to fix it. I suggest you download the latest fixes for your version and install them.

http://www.sage.co.uk/updates/line50.aspx

The users MUST have full WINDOWS access rights to the data directory on the server and their local program directory.

Users can have settings in sage set to restrict access based on the login id used to get into sage.

The easiest thing to do is to manually adjust the stock in.

Sage does not need any settings in the ODBC configuration. It just works. (well it should normally). Re installing the ODBC drivers manually should do it.

Have you had other versions of Sage installed on this PC?

What version of Sage are you running?

I don't think the year end has any thing to do with it.

The problem is almost certainly to do with the drivers for ODBC not installing properly.

I suspect you have been unable to run any reports and this is just the first time.

You need to reinstall the ODBC drivers, these are in a folder called ...

I assume you can see the payment on account on the customer account.

Which bank account did you put the payment to in the order?

I suspect you have you are looking on a different bank account to the one you have used.

If you drill into the payment on account you should see which bank account it ...

You should be able to posts transactions in May, however, you should get a warning that the transaction is outside your financial year.

This is ok, but obviously annoying, so you want to get on and do your year end, but it is ok to post with the warnings.

The goal of the warning is to prevent you ...