x Want to participate? Join the group to interact
Options
  • Replies 16 replies
  • Subscribers 58 subscribers
  • Views 7898 views
  • Users 0 members are here
Browse Forums
Sage Timeslips Anywhere Announcements
6
topics
1
replies
Sage Timeslips Anywhere General Discussion
13
topics
13
replies
Sage Timeslips Premium Announcements
57
topics
17
replies
Sage Timeslips Premium General Discussion
2k
topics
8k
replies
jamboesq

Here we go again: a redo of Timeslips 2009; Timeslips 2017, more mediocrity from mediocre programmers and software engineers

Posted By

Harkening back to the terrible, absolutely pitiful Timeslips 2009 product, Sage Timeslips and its programmers and software engineers have demonstrated yet once again that they are the most mediocre of the worst mediocrity. Here's my story: in the process of installing a completely new clean boot of Windows 10 Pro, I decided to upgrade my Quickbooks Pro 2013 to QuickBooks Pro 2016. Prior to making the upgrade I had successfully been using Timeslips 2015 with QuickBooks Pro 2013. No problems whatsoever. After installing QuickBooks Pro 2016, however, my Timeslips 2015 crashed every time I tried to open it when QuickBooks Pro 2016 was open. Being the somewhat gullible consumer that I am, I then decided that for $503 I would upgrade to Timeslips 2017. New product certainly ready to work with Windows 10 Pro, which after all, has now been around for quite a good while, right?  After installing Timeslips 2017, I then experienced exactly the same disastrous crashes every time I opened Timeslips 2017 when QuickBooks Pro 2016 was open. Now you have to believe me when I say I had all the switches and bells and whistles properly hooked up such that Timeslips 2017 and QuickBooks Pro 2016 should have easily connected. But Noooooo. Consequently, I contacted Sage Timeslips support and got an instant remedial solution.  The techie simply went into my registry and we went from Hkey local machine/software/Microsoft/Windows/current version/policies/system, then over on the right side, right clicked on EnableLUA, selected modify and changed the value from 1 to 0. Timeslips 2017 then had no problem connecting and linking with QuickBooks Pro 2016. Should have been the end of the story but nooooo. As is often the case I just happened to stumble on another Windows related problem which I would have never thought had anything to do with the fix solution that the Timeslips Techie provided for making Timeslips 2017 work with QuickBooks Pro 2016. What happened was I tried to open a JPG file and instead I got this error message “This app can't open - - photos can't be opened using the built-in administrator account.” After Googling the error message I found a solution. Although there are some other steps involved, the primary steps to fixing the error message that this app can't open require one to go to Hkey Llocal Machine/software/Microsoft/Windows/current version/policies/system, then right click on EnableLUA on the right side and change the value from 0 to 1.  What is now completely obvious to me is that Sage Timeslips and its programmers and software engineers have no idea whatsoever about how their product completely messes with Windows 10 Pro because in the process of solving the issue that Timeslips 2017 has with QuickBooks Pro 2016 the remedy screws up your usage of Windows 10 Pro where you need to have the EnableLUA value set to 1 in order to make Windows 10 Pro usable with numerous and various apps. Or put it another way: the Sage Timeslips programmers and engineers make it possible and only possible for you to use Timeslips 2017 with Quickbooks Pro 2016 if you are willing to continuously and consistently compromise the functionality of Windows 10 Pro. Idiots, total numbskull idiots. See what I mean, like they did with Timeslips 2009, a completely worthless product, they have sold us a Timeslips 2017 product that that is absolute mediocrity in all the most mediocre sense. It won’t do what it is supposed to do without one having to completely mess up the operating system in which the software is supposed to function without difficulties or conflicts. What is world is wrong with these people??!!

  • Oh, I forgot to add one more thing: Why can't they make their product like so many other software products simply and without problems or conflicts simply work seamlessly with Windows 10 Pro? I have so much other software that does not require me to tweak or alter Windows 10 Pro in order for the software to function as it is supposed to function. Can't these people figure that out?
  • in reply to jamboesq
    I disagree with you. I have found Timeslips 2017 to be a huge improvement over the previous BDE versions. I would suggest that you set the program to "run as administrator" and see if that resolves your issue.
  • in reply to Terryr
    It didn't and it doesn't; why do you think I had to finally get Support to deal with it? And that's the "official" solution. Believe me, I tried every which way to make the frickin' thing connect and/or link with Quickbooks Pro 2016. And the best they can do is what they gave me. Not cool!!
  • in reply to jamboesq
    By the way, are you running your Timeslips 2017 with Quickbooks Pro 2016? If you aren't and you aren't linking it to any accounting software, then you may not be having the issue I am having. But I need to connect my Timeslips 2017 to Quickbooks in order to keep my accounting in line for my law office.
  • in reply to jamboesq
    It may not be the issue they identified. The link between programs can be tricky. You need to make sure you can get into proper milt user mode with the server hosting multi user access. You need to make sure the program is authorized and you need to be certain that the database server manager has scanned the right paths and is running. Furthermore the server must be pointed to the database with the same path as the workstation and no machine can have keep QuickBooks running for quick startup checked in the individual preferences.
  • in reply to Caren2
    No, you are off for sure -- This is not a major office setup with a separate server and separate work stations. This is a single PC running Windows 10 Pro which, back when I was running Windows XP, I believe, you, Caren, actually first walked me through the process of connecting Timeslips 10 (?) or 11(?) or maybe Timeslips 13 to Quickbooks, which I was later able on my own to upgrade both Timeslips and Quickbooks so that Timeslips and Quickbooks "naturally" issued the certificate for connection and identified within Quickbooks the Timeslips program that was accessing Quickbooks. And as I said, Timeslips 2015 worked very smoothly with Quickbooks Pro 2013 and, previously, when I upgraded to Timeslips 2015, I did not have to re-establish the path to the Quickbooks Pro 2013 .QBW file to which Timeslips 2015 connected. Y'all need to stop being apologists for crappy software. It took a while but finally Sage had to admit that Timeslips 2009 was a total bust, piece of you know what. This has a very similar feel to it in that it should work seamlessly with Windows 10 Pro, but if the solution is what the Techie said it was, then that speaks volumes in and of itself. Moreover, if they are offering the solution they offered and you're now saying that they somehow didn't get it right then (1) why did it work meaning no more conflicts between Timeslips 2017 and Quickbooks Pro 2016 or (2) why don't they know the correct issue? I don't have this problem with any other 3d party software that's running with my Windows 10 Pro. The software is defective, no and's, if's or but's, it just is.
  • in reply to jamboesq
    And here's another thing I just thought of -- when I was running a previous version of Timeslips and a prior version of Quickbooks and then upgraded Timeslips to Timeslips 2015 while also upgrading Quickbooks to Quickbooks Pro 2013, the entire connection process was seamlessly accomplished without my having to do a thing. Nada, nothing, just so perfectly smooth. But not so with Timeslips 2017 connecting to Quickbooks Pro 2016. And that SHOULD NOT be the norm; at this point with all of the past history and relationship, the two programs should "marry" without the user having to get overly technical or spend more money with consultants just to make the damn thing function correctly. That's like buying a new car and having to have your mechanic make the engine work correctly.
  • in reply to jamboesq
    I am not trying to totally defend Sage but I will tell you that with updates to QuickBooks 2016 I am seeing a lot of having to reestablish the connection, not only with Timeslips bit with other applications as well. It may have something to do with the new security enhancements in QuickBooks.
  • in reply to Caren2
    Caren: What I'd really like to know is whether there is just a Single, Solitary fix to the issue, that is, is there one set of processes or steps that will enable Timeslips 2017 to connect or link to Quickbooks 2016 without altering or modifying Windows 10 Pro?
  • in reply to Caren2
    We have others working with the combination without problems on Windows 10. I can't make guarantees but I can tell you I have never changed registery settings to get the link working. I do sometimes right click and set it to run as administrator.
    I'd be happy to speak with you. Will be back in office on Thursday

*Community Hub is the new name for Sage City