Mr Defense

Spoke too soon! 3:33 got my 1st error in 2 days. We are making progress, I think things are getting better.

Irv

To clear a few things up, the original post to MOMFAQ was not posted on this site until 2/23/07. I posted it to a restricted area and thought it was lost and pretty much forgot about it. Today an Admin from this site found it and posted it.

In fairness to Dydacomp I am posting their response to my email:


Dear Irv Miller:

I certainly understand your frustration with this part of the software and I want to assure you that everyone is working hard on making the necessary changes.

Rather than get into a finger-pointing contest with one of our most trusted partners, let me assure you that we are working closely with Harvey so that a suitable solution can be delivered as quickly as possible. We are also in the process of further addressing how to best communicate and coordinate with these third parties upon the pre-release of such a major upgrade that also has database changes. In fact, Harvey will potentially release a beta patch by Wednesday of next week, February 14, 2007. I supplied your contact information to their support staff so they can contact you directlty, regarding the release of this patch.

As much as it was disheartening to hear of your current situation, your positive words about your use of the software is an indication of the process that we successfully employ to work through any reported issues. Indeed it seems that you've been through this process before in 2003 when upgrading from M.O.M. version 4.0 to M.O.M. version 5.0. While any pre-release version of the software will have issues, our ability to resolve a reported issue speedily is part of our strength. Overall, we are very encouraged by the response that we've been receiving about the feature set and the functionality of the M.O.M. 6.0 software and it is being used in production by scores of clients to run their daily operations.

Of course we will continue to work with you and are giving this matter the highest priority. A senior member of our staff will keep you updated. You are welcome to contact me or any other member of the Dydacomp team when we can be of further assistance.


Regards,


Albert Realuyo
VP/Product Development
Dydacomp


Many bugs and errors have happened since then. Dydacomp has been working with me daily to resolve them. There were many small things that I send errors on and hear nothing and then the next update they are corrected. An email to let me know it was corrected would be swell, but that is not happening.

After two very long weeks and many hours of wasted time, I think we may be leveling out with the program. I am updating every day and (knock on wood) for the last two days I have not seen an error. Of course it is only 2:30 on Friday :-)

So maybe there is light at the end of the tunnel. If I can go a week without errors I will post here and say I think 6.0 is ready. We are heavy users and we put it to the test.


Irv

Yes, but it did not say much. No offer to do anything for my time etc.
In fairness to Dydacomp, I will post the response message below.
Also for the record, this post was in limbo on this site because I somehow posted it to a restricted area on 2/8/07. It was posted here today 2/23/07 even though the original post date is marked 2/8/07.

Irv

It's been several weeks since you posted. Did you get any response from Dydacomp?

Best,
Tom

Well it looks like Harvey has been doing a work around. After better than 2 weeks with no OBDC functionality, Harvey got me the beta version at 5:00 p.m. on Friday 2/16. I installed it and Harvey is now talking to MOM 6.0's boxshare.dbf file.
Monday will be the test. I hate to say it, but I think all the 3rd party vendors and custom OBDC integration will need to be reworked to work with Foxpro 8.

Irv

I am not sure about RR or Chrystal, but I do use Harvey for my shipping. The day we upgraded to 6.0 we lost the OBDC connection and Harveysoft was caught off guard. They had no idea about the database changes. The way I understand it is Dydacomp went to Foxpro 8 which has completely different structure than all previous versions. From January 29th until 5:00 yesterday we did not have a Harvey communication with the boxshare.dbf.
Harvey scrambled to correct it. I have the new beta version and it is working. I will see on Monday how well it holds up.
Since Harvey lost total communications with boxshare.dbf when the upgrade happened, I would assume that all 3rd party software developers who were using old versions of Fox Pro for OBDC communications will not be working until they are upgraded. From what Harvey told me it is a major change.

Irv

Is anyone using RR or Crystal Reports with ODBC Connections and MOM 6.0?

I ask because they don't seem to work and neither do ODBC Connections to Harveysoft or Access... Dydacomp says "not our issue" so looks like those of us who upgraded without being told these things don't work are stuck...

I believe this could be a simple configuration issue but no one seems to be able to resolve it

Any Ideas?