Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

One single project for all?

2 posts in Commercial ISV's Last posting was on 2009-10-15 16:53:38.0Z
"Manuel Espinoza" <jmespinoza_no_spam Posted on 2009-10-08 20:40:42.0Z
From: "Manuel Espinoza" <jmespinoza_no_spam@seicom_dot_com_dot_mx>
Newsgroups: sybase.public.commercial-isv.general
Subject: One single project for all?
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4ace4e4a$1@forums-1-dub>
Date: 8 Oct 2009 13:40:42 -0700
X-Trace: forums-1-dub 1255034442 10.22.241.152 (8 Oct 2009 13:40:42 -0700)
X-Original-Trace: 8 Oct 2009 13:40:42 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.commercial-isv.general:319
Article PK: 104032

Re-posted from the general news-group:

-------------------------------------------------------------------------------
Hi!

I've been asked on how to keep all in one, I mean, we sell mainly an ERP
system that is modified/adapted to every client's needs, so the normal way
of working is take the latest version and then begin the modifications from
there. The 'problem' comes when a bug is reported, then solved for a
particular version. Then we have to 'remember' to correct it (if apply) on
the others versions.

So for an easier maintenance, we are looking for some way to keep one single
project for all clients, and then keep some structure where we can define
for an instance, for client A open(w_window_A), for client B,
open(w_window_B) where each window is basically the same, but adequated to
each client requirement.

Is this feasible? any experience? Pros /cons?


M. Searer Posted on 2009-10-15 16:53:38.0Z
From: "M. Searer" <nospam@nospam.com>
Newsgroups: sybase.public.commercial-isv.general
References: <4ace4e4a$1@forums-1-dub>
In-Reply-To: <4ace4e4a$1@forums-1-dub>
Subject: Re: One single project for all?
Lines: 35
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4ad75392$1@forums-1-dub>
Date: 15 Oct 2009 09:53:38 -0700
X-Trace: forums-1-dub 1255625618 10.22.241.152 (15 Oct 2009 09:53:38 -0700)
X-Original-Trace: 15 Oct 2009 09:53:38 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.commercial-isv.general:323
Article PK: 104035

we use a patch.pbd to put out fixes to all customers.

For customizations of windows, we use inheritence to put all custom code in a separate layer than the standard code.
All custom code goes in a custom.pbd.
So, the window names are all the same across all customers, but the code in the custom.pbd controls what is actually being done.

Library list order is:
custom.pbd(s)
patch.pbd
application.pbds

"Manuel Espinoza" <jmespinoza_no_spam@seicom_dot_com_dot_mx> wrote in message news:4ace4e4a$1@forums-1-dub...
> Re-posted from the general news-group:
>
> -------------------------------------------------------------------------------
> Hi!
>
> I've been asked on how to keep all in one, I mean, we sell mainly an ERP
> system that is modified/adapted to every client's needs, so the normal way
> of working is take the latest version and then begin the modifications from
> there. The 'problem' comes when a bug is reported, then solved for a
> particular version. Then we have to 'remember' to correct it (if apply) on
> the others versions.
>
> So for an easier maintenance, we are looking for some way to keep one single
> project for all clients, and then keep some structure where we can define
> for an instance, for client A open(w_window_A), for client B,
> open(w_window_B) where each window is basically the same, but adequated to
> each client requirement.
>
> Is this feasible? any experience? Pros /cons?
>
>
>