Solution migration best practices

Questions and answers on designing your Servoy solutions, database modelling and other 'how do I do this' that don't fit in any of the other categories

Solution migration best practices

Postby Riccardino » Wed Aug 25, 2004 12:39 pm

Hi,

I need to build a new solution (an invoicing system) and I'd like to use parts of a completely different solution (some tables, methods, buttons, methods).

Which approach do you suggest in order to minimize development time?
ciao, ric
User avatar
Riccardino
 
Posts: 911
Joined: Thu Apr 24, 2003 11:42 am
Location: Ferrara, Italy

Postby Bert » Wed Aug 25, 2004 1:36 pm

Good question Riccardino!
Because I've got a simular situation over here.
I'm building a little To-Do-List-solution wich should be part of a major office-solution in the (near) future.

Maybe someone has some general answers or workarounds regarding these issues.

TIA :)
Bert de Graaff
ATB Software Servoy Developer manage your business anywhere
User avatar
Bert
 
Posts: 201
Joined: Tue May 20, 2003 11:16 am
Location: Stramproy - NL

Postby Jan Blok » Wed Aug 25, 2004 3:32 pm

Currently do an importAS of the solution you want to reuse, in Servoy 2.5 it will be possible to load solutions in other solutions as modules.
Jan Blok
Servoy
Jan Blok
 
Posts: 2684
Joined: Mon Jun 23, 2003 11:15 am
Location: Amsterdam

Postby Providence1 » Thu Aug 26, 2004 2:55 am

For those that don't know or can't find it, what is an ImportAS?

Thanks!

Providence
Providence1
 
Posts: 456
Joined: Tue Aug 17, 2004 2:36 am
Location: New York, NY

Postby Jan Blok » Thu Aug 26, 2004 10:26 am

File menu->repository-> import ->import as
Jan Blok
Servoy
Jan Blok
 
Posts: 2684
Joined: Mon Jun 23, 2003 11:15 am
Location: Amsterdam


Return to Programming with Servoy

Who is online

Users browsing this forum: Google [Bot] and 40 guests

cron