Sage 100

I don't have a contact for you as the only times I've had to deal with support was to get a new license for server moves or upgrading from version 9 to version 10.  There was one other case I submitted to support that had to do with queries timing out in version 10 that worked fine in version 9 because version 9 didn't implement a timeout option whereas version 10 implemented a very short timeout, something like 30 or 60 seconds.  Took over a year and a half for them to implement a user configurable option in the latest release of version 10 (10.0.4) that allows setting the timeout up to a maximum of 180 seconds.  I asked them to make it where it would except larger values or even allow disabling the timeout entirely because let's face it, rather than babysit a report or query that might run for a while, Sage Alerts is the perfect solution to have such a report or query scheduled but having such a short timeout defeats the purpose.

If you have more insight into what is happening, I may be able to provide some insight.

FYI, version 9 had a funny behavior where if both email 1 and email 2 were not populated for a subscriber, no deliverable was created, whereas in an upgrade from version 9 to version 10 or out of habit you set up a subscriber in version 10 with both email 1 and email 2 populated, then version 10 will send the deliverable to each email even if they are identical.

I don't have a contact for you as the only times I've had to deal with support was to get a new license for server moves or upgrading from version 9 to version 10.  There was one other case I submitted to support that had to do with queries timing out in version 10 that worked fine in version 9 because version 9 didn't implement a timeout option whereas version 10 implemented a very short timeout, something like 30 or 60 seconds.  Took over a year and a half for them to implement a user configurable option in the latest release of version 10 (10.0.4) that allows setting the timeout up to a maximum of 180 seconds.  I asked them to make it where it would except larger values or even allow disabling the timeout entirely because let's face it, rather than babysit a report or query that might run for a while, Sage Alerts is the perfect solution to have such a report or query scheduled but having such a short timeout defeats the purpose.

If you have more insight into what is happening, I may be able to provide some insight.

FYI, version 9 had a funny behavior where if both email 1 and email 2 were not populated for a subscriber, no deliverable was created, whereas in an upgrade from version 9 to version 10 or out of habit you set up a subscriber in version 10 with both email 1 and email 2 populated, then version 10 will send the deliverable to each email even if they are identical.

I don't have a contact for you as the only times I've had to deal with support was to get a new license for server moves or upgrading from version 9 to version 10.  There was one other case I submitted to support that had to do with queries timing out in version 10 that worked fine in version 9 because version 9 didn't implement a timeout option whereas version 10 implemented a very short timeout, something like 30 or 60 seconds.  Took over a year and a half for them to implement a user configurable option in the latest release of version 10 (10.0.4) that allows setting the timeout up to a maximum of 180 seconds.  I asked them to make it where it would except larger values or even allow disabling the timeout entirely because let's face it, rather than babysit a report or query that might run for a while, Sage Alerts is the perfect solution to have such a report or query scheduled but having such a short timeout defeats the purpose.

If you have more insight into what is happening, I may be able to provide some insight.

FYI, version 9 had a funny behavior where if both email 1 and email 2 were not populated for a subscriber, no deliverable was created, whereas in an upgrade from version 9 to version 10 or out of habit you set up a subscriber in version 10 with both email 1 and email 2 populated, then version 10 will send the deliverable to each email even if they are identical.