NOTE: Our mvBase (from General Automation, version 1.3.02) runs on
Windows NT 4.

After rebooting the Windows NT server, we are no longer able to print
within mvBase. Mind you, from Windows NT I can print, so it's
definitely not a Windows problem.

Strangely, the printers show "inactive" status in the PICK system.
Since I'm new to my company and this computer, I don't know if that's
normal, but probably it isn't normal.

Anyone seen this problem before?
Know how to fix it?

We're desparate here.

Thanks.

Start with some basics:

Is the workstation service running?

Are the printers started in mvBASE? Do a LISTPTR and make sure
they show up.

In the workstation printer definition, is the Disable checkbox
ticked? Obviously, it shouldn't be.

Likewise, can the workstation see the windows printer? If you
change the location of the printer in the windows network, mvBASE won't
automatically follow.

You haven't changed printers have you? GDI and LDIL printers won't
print from mvBASE.

Cheers,

Brian Speirs


Adam wrote:
--
************************************************** *
Brian Speirs
h: (04) 479 9032 c: (021) 265 5906
e: bss59REMOVETHIS (AT) paradise (DOT) net.nz

Adam, mvBASE is now owned and supported by Raining Data Corporation.
It was acquired from General Automation about 5 years ago. Someone
here in this forum might be able to help, but if not you can get
support from RD. Their Support number in the USA is 949
442 dash 4400. You will have to speak to someone in Sales who can
give you information about how to get through to Support. I'm sure
you will need to pay some premium since your system is no long on an
active support agreement. Note that the latest release of mvBASE is
2.0, but 1.3 is fine too.

If you are new to the environment and you have no other support I
highly recommend you take steps to find someone here who will provide
you regular support. Please tell us what part of the world you're in
so someone nearby might be able to volunteer or solicit services. I
further advise in your case that you take steps to migrate to another
Pick-based environment which is supported and less subject to hiccups.
there are many eligible candidates - it would help if you could tell
us how many users you have connected to your system. I dare say your
NT4 is a bit dated too. If you need assistance with your business
software, you may find someone here who's qualified to work with it -
if you know the name of the software package that might help. You'll
usually see this when you login to your main account.

I won't hassle you about upgrades or support, I understand you have a
fire to put out. I'm sorry but I can't offer any advice to solve the
technical problem.

Good luck.
Tony Gravagno
Nebula R&D
TG@ removethisNebula-RnD
..com

"Adam" <adammorris70 (AT) hotmail (DOT) com> wrote:

Tony Gravagno wrote:

Yes, we plan on replacing the software, but for now, as you say, I have
fire to put out. We're trying to get help from Raining Data, but it's a
little difficult. They can't even find our records. And yes, I'm trying
to locate experts still.

In fact, I found one person who helped me troubleshoot. He determined
that PICK wasn't the problem. And again, Windows NT isn't the problem
either.

Possibility #1:
Is there a layer of software in between PICK & NT that could be a
problem?

Possibility #2:
By coincidence, earlier the day we lost printing capability, a
Windows-based workstation connected to a PICK printer. That's never
been done before. The printer was dedicated to the PICK server. The
PICK server itself connects via network cable to another server (a file
server w/W2k) which offers the availability of printers including that
one.

Could that some how cause a problem with printing? Again, the other
server prints fine to printers. The Windows NT on the PICK server
prints fine too, but PICK itself that lies on top of it, can't print
despite the fact that PICK thinks it did print.

Yes, it was checked!!

And I don't know why.

Bizarre!

My only theory is that the PICK printer, which has its own print server
box (w/ bi-directional messaging), sent a message back to PICK that
PICK didn't understand. PICK reacted by checking the "disable printer"
checkbox. That happened right after I had a new PC talk to the PICK
printer ("Add Printer" on the PC). So the printer should remain a
dedicated PICK printer.



Anyway, thank you, Brian.
You're the hero of the day!

And Tony, thank you for your time, too.
Can't wait until we replace that old system with a new ERP!

-Adam

Adam,

As a lurker, it was gratifying to see CDP come through again.

However, your conclusions are wrong. You don't need to replace your
entire "ERP" system.

In fact you might find such a project to be less than fun.

For a much smaller investment, you could bring your current system up
to date.

Please don't throw the baby out the with bathwater.

As Tony asked, where are you located? There are many Pick Consultants
that could help you.

douglas (AT) pickteam (DOT) com wrote:
Douglas,

Actually, the problem is that we don't have an existing ERP system. Our
business software, which runs on PICK, lacks essential integration with
accounting and other key modules like other ERP solutions tend to have.
On top of that, the business logic of the software is just plain awful.
And the software is quite buggy to boot.

Just to give some background, this software was 100% customized for us
a long time ago; and the company that developed it no longer exists.
We were taken advantage of by unscroupulous programmers. We think this
"baby" should go after all the pains and money it cost us to keep it
alive. I wouldn't mind having access to some local PICK experts, but
only to maintain the system during the phase out interim, not to
upgrade it. We're based within the Los Angeles County area if you know
any experts.

In so far as implementing a new ERP solution goes and the anticipated
problems that goes along with that, that's really not a big issue for
us. We're going with Microsoft. Microsoft has a program where they
intervene on any of their partners implementation projects should their
system not be properly implemented. Microsoft will make sure that it
gets done. Their reputation depends on it. We're going with a solution
that basically is more designed for our industry as well as the ability
to better cater to big name customers we've acquired these last few
years. One main feature needed is FDA regulated tracking.

Anyway, that's our story.

-Adam

Nevermind problem solved

The "disable print" checkbox was checked

The PICK system did this itself for some reason

Could be because it didn't like sharing a printer with a Window
computer (which it no longer does)

The printers now works

Adam wrote:
Glad to help. I know how frustrating these things can be.

It seems a shame that you are getting a bad impression of MV systems due
to bad software. Your underlying MV system is quite stable, but all you
see is the buggy software on top of it!

Consider the comments made elsewhere in this thread carefully. Make
sure your new system really does deliver what you want. We (the PICK
community) would hate to see you jump from one sub-optimal solution to
another.

Cheers,

Brian
--
************************************************** *
Brian Speirs
h: (04) 479 9032 c: (021) 265 5906
e: bss59REMOVETHIS (AT) paradise (DOT) net.nz

Tony Gravagno wrote:

Spot on!

This thread really does highlight a lot of the problems we are facing:

Buggy software gets blamed on MV.
Old hardware and OS means slow performance (blamed on MV again).
Few people know how to support MV.
mvBASE has limited connectivity to the rest of the world (therefore
other flavours get implicated as well).
See threads elsewhere on licensing costs, support etc.

MV used to be a cost-effective solution offering multi-user computing at
a fraction of the cost of other solutions. The cost effectiveness came
from lower per seat costs and lower hardware requirements. But in the
last 20 years:

Hardware costs have plummeted while performance has increased.
Desktop databases have extended up into the workgroup
Open source systems have carved up the small server market
Users expect graphical interfaces

In the small server market:

Cost of hardware is no longer an issue
The expensive old solutions have been replaced by desktop/open source
solutions.

MV today is no longer a low-cost solution. Nor does it have the cachet
of Oracle, SAP, or even SQL Server. That combination makes it pretty
hard to capture new customers - or even to maintain existing customers -
and that is the nub of the problem.

It has all been said before - but here we have another example of
someone jumping ship.

Have a good weekend everyone!

Brian Speirs
brian at rushflat dot co dot nz