Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 5637 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

We are planning on upgrading our FMS 9 Advanced installation to FMS 10 Advanced. We also have several Access databases and a number of tables within those databases that read and write data to the FMS databases using the SequeLink driver. My question is whether the upgrade process also requires us to do some work with the connections in the Access database. (As in, do we have to open the Access databases to recreate each of those connections?)

I know the documentation discusses that the SequeLink driver provided with 10 is an upgrade from previous version, but I wasn't sure if is specifically an upgrade from what comes with FM9, as the SequeLink installer file with each FM version indicates that they are both version 5.5. It gave me the impression that I wouldn't have to do any upgrades for the drivers. If we have to then we have to, but it is important to be aware of in advance.

Thanks!

Posted

I dont think so. The driver never changed as you already found out.

  • 2 months later...
Posted

I've recently upgraded to FMSA 10 and installed a copy of FM Client 10 on the same server (did not install IWP with the client). Not sure if its a coincidence but I have started getting the error "DataDirect SequeLink Server for FileMaker encountered a problem and needed to close"

We've had troubles with the software that's connecting to the server via ODBC give is trouble in FMSA v 9 but this is a different error with different issues. Could it be related to having client installed on the same machine as Server?

I noticed in this thread that SequeLink version that installs with 10 Server is 5.5 but there is now a version 6 on their site. Is the upgrade as simple as installing the new version from their site or are there other tie-ins to FM Server. 6.0 also doesn't appear to be a free upgrade.

Hopefully that made sense.

TIA

Posted

I havent tested version 6 there was someone the other day that I was helping that coincidentally was having issues with ODBC and they had version 6; could be just a coincidence or maybe not.

Also I wouldnt run client on the same machine, especially if you have the ODBC option turned on for both client and server. They both should be using the same port 2399

Posted

thanks i'll remove client from that machine. it wasn't necessary it was something i thought would be nice to have.

This topic is 5637 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.