To answer the other questions:
I would gain ODBC access with MS Access to the Invoice Header/Line Tables,
Customer and Product Tables. I would maintain in Access a table of those
Invoices already converted. I would then create a CSV export of the new
Invoices and current Customer/Product tables
I had a client that attempted just what you are doing. After 2 years, and a
little over 2 million dollars spent, they went back to their home grown
UniVerse system. I will not go into the gorey details of the nightmare, but
will summarize with this: limited customization, double billing, double
This sounds very tempting, using MV as a data warehouse to a non-MV (or MV)
primary application. Does anyone else have any insight on how this flies,
management-wise or technically.
I like it as all of the original reports are already written and tested and
it keeps the customer a MV customer.
Users Discussion List [EMAIL PROTECTED]
Sent: Sunday, April 04, 2004 12:55 PM
Subject: Re: Conversions
Mark,
Technically Overview:
Using some sort of a schedule, you identify new and modified data
on the Great Plains system, and move just that data to the MV system,
converting
In a message dated 4/2/2004 10:06:39 PM Pacific Standard Time,
[EMAIL PROTECTED] writes:
Tony,
Stupid question... If you and I built a company which was strictly
Hey my name's not Tony but if there's money involved you can call me anything
you want.
Will
--
u2-users mailing list
PROTECTED]
Sent: Saturday, April 03, 2004 9:50 AM
Subject: RE: Conversions
Mark -- I don't have experience with Great Plains, but can definitely
sympathize with your situation. I have been on both the technical and
management side of such conversions.
Given that it sounds like the decision has
Mark,
Tell them you are re-purposing the old MV system as a data warehouse
as a cost savings measure. That they'll understand and hopefully
appreciate. Then do what you suggested:
One strange thought occurred to me that may not fly. Export all the
sales/customer/product data back to the MV
Mark,
As a Business Process Consultant (one of my hats), here's how I
would approach it.
1. You are already moving in the correct direction by pointing up
productivity loss, but you have to frame the argument correctly:
1. We have implied and explicit deadlines in serving our
You have my sympathy/empathy, and I'm sure that of many others here. I have
some thoughts that may seem common sense, but they may be worth mentioning:
Document everything.
-- Downtime
-- Delays
-- End-user complaints
-- Discussions with management and software vendors
-- Missing features,
Please IGNORE last post. It was meant to be private. I was meant to be
asleep.
Sincerely,
Charles Barouch
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
Smooth bro. Real smooth.
Excuse us ladies and gentlemen as I escort our colleague out by his ear and
smack him around a little.
Please IGNORE last post. It was meant to be private. I was meant to be
asleep.
Sincerely,
Charles Barouch
--
u2-users mailing list
[EMAIL PROTECTED]
11 matches
Mail list logo
