Jump to content

Sync Abort: No table properties provided


Valentin Vollmer
 Share

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

Recommended Posts

  • Newbies

Hi Jesse,

thanks for the reply. Just now I more or less accidentally figure out what is going on: the client was using an older version of that database where that table did not exist yet. So when the Server tried to communicate it failed. Reconfiguring the sync script without that table, syncing and updating the client (spoke) file did the trick. 

I am not sure whether or not I am correct about this, but I believe this did not seem to be an issue before the latest update. I was able to add tables on the hub and then role out the changes to users individually when they needed to start using those new tables. Again, not sure if that is correct.

Link to comment
Share on other sites

Valentin, you are right - we did some testing and it does cause a problem to add a new table to the sync, if you're syncing with a device with an old sync script. This did not used to cause a problem. We will check into what change we made caused this and put it back the way it was before.

Link to comment
Share on other sites

  • 2 weeks later...

This topic is 2351 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
 Share

×
×
  • Create New...

Important Information

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