Filemaker 5 compatibility in recent Windows OS

[bilbod]

Hello,

I have a solution with several users made the Developer 5, so, they are runtime solutions. They have installed and performed will, for me, right up through today's updates for Windows 8. However, a user with Win7 cannot get the runtime to function even after we both went through permissions and compatibility fairly thoroughly. The Win 7 machine did an update on the 13th and the system that had worked well there won't open now and it is being flagged as a compatibility issue. We've tried many configs of that and have bottomed out. Is there a way to tell Windows to just bugger out?

Thanks,
Bill

[bilbod]

I think I found the issue tho am not sure of its origin. To be more clear, it is Vista that the FMP5 runtime would not open in. It was installed in C: to avoid that multiple user/multiple files that Windows is doing now with installations in Program Files. Well, I moved runtime solution into Program Files and it runs! Anyone know if MS released an update that locked programs down to Program Files in Vista? This solution still runs well in C in my Windows 8 machine.
Bill

[Helpful Harry]

In article <d0e94ebc-9b41-4984...@googlegroups.com>, bilbod

I don't think Vista is "locked down". I've got a FileMaker 4.1 runtime
application that has been running under Windows XP, but the client has
just upgraded to a new(er) computers with Windows 7 and the runtime seems
to be working properly without being in the Program Files directory.

The only issue is that the document files lost their link to the runtime
application so you have to double-click the runtime application itself
rather than any of the document files. Their computer was only upgraded
yesterday, so I haven't yet looked into fixing that problem.

They also have a second FileMaker 4.1 runtime they use (also not stored in
the Porgram Files directory) and I haven't been phoned / emailed about any
problems with that not working either.

Helpful Harry :o)

[bilbod]

Thanks Harry,

Not sure what was happening on the one Vista machine but it concerns me that others may be having issues with our download and not hearing about it.

BTW, isn't it interesting for a DB system to have completely different sets of files for each user when the system is installed in Program Files [Vista forward]?

Best regards,
Bill

[Helpful Harry]

In article <1bc702f0-2964-4074...@googlegroups.com>, bilbod

<bja...@montanaport.net> wrote:
>
> Thanks Harry,
>
> Not sure what was happening on the one Vista machine but it concerns me
> that others may be having issues with our download and not hearing about it.

It probably doesn't make any difference, but I should have said that my
FileMaker 4.1 runtime applications were created unsder Windows 95 (under
Virtual PC on my Mac), but the client was running them under Windows XP
and now Windows 7.

They have no issues other than the linking problem I mentioned ... at
least, they have no issues with my FileMaker databases. They are having
massive issues with the new server and cloud based email they've had
pushed on them by their "expert" IT company. Those "experts" have already
spent most of the week trying to get it all working. :o\

> BTW, isn't it interesting for a DB system to have completely different
> sets of files for each user when the system is installed in Program
> Files [Vista forward]?

I haven't had to deal with Windows 7 until now (although one person does
have a new Windows 8 laptop, and boy is that a mess of an operating
system!). The runtime applications I created under Windows 95 work fine by
simply copying across the whole folder / directory. They aren't doing
anything hugely fancy, so don't need any extra files stored in the Windows
system directories.

Helpful Harry :o)