Thanks, Guy. I'll definitely check it out.

On Tue, Aug 30, 2016 at 6:57 PM, Guy Algot <[email protected]> wrote:

> No problem Doug. If it changes let me know.
>
> You probably want to visit the Foundation page and upgrade your component.
> There’s also a support list over there as well.
>
> > On Aug 30, 2016, at 5:03 PM, Doug Hall <[email protected]> wrote:
> >
> > Thanks for the responses so far! I'm so glad I still have help here! (I'm
> > gonna need it.) How wonderful to hear from some of you old-timers -- all
> > the way back to the CompuServe days (Douglas von Roeder and Lee Hinde for
> > sure, and Chip Scheide might have been around in those days. My memory
> > fails me.) I can hear that blasted 9600 baud modem screeching, to this
> day!
> > :-))  <--- Yes, I've adopted a double chin, now. Gotta get rid of that
> > stupid thing. :-((
> >
> > After a little plowing through 4D Insider, I've found a few plugins that
> I
> > wasn't even using, but never bothered to clean out. I've already
> > removed Expat4D, 4D Open and PrintList Pro. I had already removed the MD5
> > plugin I mentioned earlier, but I had forgotten I had. (I was working off
> > an old list of plugins.)
> >
> > Before I waste more of your time, I'm going to need to dive into the
> > upgrade manuals and do some further preening of my code, to make sure
> that
> > I'm only porting the code that I'm actually using. 4D Insider will help
> me
> > locate stuff I'm not using. By the way, is there a replacement for that
> > functionality now that there is no more 4D Insider?
> >
> > I am glad to hear that it's actually possible to go straight to v15. I'm
> > going to have lots of questions along the way. I hope you guys don't get
> > tired of me.
> >
> > Guy Algot, I appreciate the offer of help, but we're pretty low budget in
> > this state office. Just upgrading the software is sending shock waves. I
> > appreciate the offer, though.
> >
> >
> > On Tue, Aug 30, 2016 at 4:45 PM, Chip Scheide <[email protected]
> >
> > wrote:
> >
> >> as for BASH:
> >> list which methods in it you are using.  THere are likely bits of code
> >> out there to replace the functionality (if 4D has not already done that)
> >>
> >>
> >> On Tue, 30 Aug 2016 16:17:26 -0500, Doug Hall wrote:
> >>> For various reasons, we have put off upgrading 4D. We originally
> intended
> >>> to just move off of 4D all at once, but that turned out to be
> impossible.
> >>> I've added onto our existing structure in spurts, but for the most
> part,
> >>> I've been out of active 4D development for almost a decade, now.So,
> now I
> >>> begin the journey of a million miles, with a single step. The first is
> >>> advise from you guys. Should I shoot for an interim version, say v13,
> or
> >> is
> >>> it possible (practical) to go all the way from 2004 to v15?
> >>>
> >>> I know that the Bash component we're using has not been supported for
> >>> years. Has anyone reverse engineered the methods in this component? If
> >> so,
> >>> please email me privately.
> >>>
> >>>
> >>> Here's what we're currently using in 4D 2004:
> >>>
> >>> Foundation (v3.7.2?)
> >>>
> >>> Components:
> >>> Bash Component: I've heard there is no way to upgrade. Please advise.
> >>> Rollover (Used by ToolBar) No longer available.
> >>>
> >>> Plugins:
> >>> AreaList Pro 7.9
> >>> Active4D
> >>> MD5 Plugin
> >>> PDF Plugin
> >>> PostgreSQL Plugin
> >>>
>
>
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************
>
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to