This is the effect of the User Account control (UAC) which was added in Windows Vista in 2006. When you map drives at logon, they are mapped with the filtered token (standard rights). When you now run an application elevated (with full admin token) it can't see the mapped drives of the normal permissions.

When network shares are mapped, they are linked to the current logon session for the current process access token. This means that if a user uses the command prompt (cmd.exe) together with the filtered access token to map a network share, the network share is not mapped for processes that run with the full administrator access token.

To allow admin programs to see the normal mapped drives, enable the setting EnableLinkedConnections

Click Start, type Regedit in the Start programs and files box, and then press ENTER.

Locate and then right-click the registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.

Point to New, and then click DWORD Value.

Type EnableLinkedConnections and then press ENTER.

Right-click EnableLinkedConnections and then click Modify.

In the Value data box, type 1, and then click OK.

Restart the computer.

As a general guide, do not map drives under an Administrative account.

Norman
 

This is the effect of the User Account control (UAC) which was added in Windows Vista in 2006. When you map drives at logon, they are mapped with the filtered token (standard rights). When you now run an application elevated (with full admin token) it can't see the mapped drives of the normal permissions.

When network shares are mapped, they are linked to the current logon session for the current process access token. This means that if a user uses the command prompt (cmd.exe) together with the filtered access token to map a network share, the network share is not mapped for processes that run with the full administrator access token.

To allow admin programs to see the normal mapped drives, enable the setting EnableLinkedConnections

Click Start, type Regedit in the Start programs and files box, and then press ENTER.

Locate and then right-click the registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.

Point to New, and then click DWORD Value.

Type EnableLinkedConnections and then press ENTER.

Right-click EnableLinkedConnections and then click Modify.

In the Value data box, type 1, and then click OK.

Exit Registry Editor, and then restart the computer.

Norman
 

This simply means that you are not looking in the same data directory!

This is usually associated with mapping drives and the mapping is different.

When you do a major update to Sameday Express which involves file structure changes then the system will backup the current data into a directory under the existing data directory.

The chances are that the computer that 'sees' the old data is mapped to a backup and not the data directory.

Make sure you have not set the mapped drive to 'Always available offline' . This will cause chaos.

Norman
 

The 32 bit version of Outlook is compatible with TPN Invoicing up to and including 2016. TPN Invoicing uses Simple MAPI to send invoices and this is part of Outlook.

Outlook MUST be set as the default Mail handler in Default Programs. You should check that it is associated with MAPI.

If TPN Invoicing was working properly before you installed a new version of Outlook and you can no longer email invoices then the solution lies within Outlook. You should seek assistance from the original supplier. Recently Microsoft has been making extensive alterations to the Control Panel and Default Programs in Windows 10 and assistance may require expert advice. It seems that there are currently problems with the latest Outlook 2016 using MAPI to send emails which is reported by Sage, Quickbooks and myob. These concern a corrupted Registry entry key for Outlook and require that you run the Modification option in Office to attempt a repair.

You can also try to test TPN Invoicing by running Outlook as an Administrator then going into File and Options. Go into the Trust Centre. Click on the Programmatic Access link on the left. Click on the 'do not warn' option and Save. Now try the emailing again. The emails should appear in Sent Items and shows that the issue is to do with Windows security.

It is suggested that rather than emailing all the invoices you go into Reports/Invoicing/CSV data and put in an invoice number. On a temporary basis you can set the Account Email of the associated account to your own email address so that you can immediately and easily check this.

If the current oddities with Outlook 2016 are not resolved quickly enough by Microsoft then you can install an alternative Email Client, such as Thunderbird, set this up and then set your default Email Client in Default Programs to this. You can use Outlook as normal, but MAPI will run through Thunderbird instead. When this works it simply proves that the original problem lies in Outlook.

Norman
 

This has just occurred. 22nd May 2018.

Running a MacBook Pro with a non-Apple power supply which has been working happily for two years. All of a sudden it no longer works and will not charge or connect.

After a visit to an Apple repairer it seems that the requirement to use only Apple products has somehow been invoked. Replacing the PSU with the official Apple Magsafe 2 resulted in a restored system.

The non-Apple PSU works and will charge every so often, say 1 in 100 connection. But not good enough for our requirements.

Norman