Axiant Users

[Darren Reely]

John,

Your tips has just convinced me that Axiant needs a little more maturity.  
<RANT ON>
What can I say.  I'm sick of having to keep these types of problems in mind
for each piece of software I use.  Especially anything that runs on the MS
Windows platform, which has caused me many more headaches than any other
software.  Hmm... Biting tongue...
</RANT OFF>

Thanks for the invaluable write up.  I'll save it just in case I have to
use Axiant in the near future.

Darren.


Mackin John wrote:
> 
> I have been using Axiant for 3 years now, with a number of successful
> implementations.  Axiant used to crash a lot during development but this was
> much improved with Axiant 3.  One word of advice though - don't try running
> the development environment on Windows 9x it always seemed to produce a lot
> more crashes than NT - I now recommend a minimum spec of NT Workstation with
> 128Mb RAM, and this seems to provide a fairly stable development
> environment.
> 
> As for deployment environments, I have only used Thin Client deployments.  I
> have worked on implementations using Win 9x, NT 4, Win 2000 and XP clients
> with NT, Win 2000, HP/UX and DG/UX servers.  All implementations use an
> Oracle database either on the application server, or on a third tier
> database server (NT, Win2000, HP/UX, DG/UX or VMS), Oracle versions vary
> from 8.0.5 to 8.1.7.
> 
> I had some experiences with Powerhouse and Sybase a few years ago - it was
> more painful than upgrading our 5000 program system to axiant.
> 
> A few tips that can help with axiant stability:-
> 1) Don't save your work in workspaces - always commit it to the repository
> 2) If your repository is on a network disk, make sure the network is
> reliable - network failures often caused axiant to hang
> 3) Commit and completely close then re-open the developers workbench
> regularly this frees resources and makes things faster and more stable.
> 4) If migrating existing programs, always use a new workspace, migrate,
> commit and then close axiant immediately.
> 5) Watch out for remote timeouts - if you try to remote build a program on
> Unix after the timeout you'll lose your work.  Use Remote Disconnect if you
> are logged in and not going to be building programs regularly.
> 
> John Mackin
> jmackin@azurgroup.co.uk
> 
>         > -----Original Message-----
>         > From: Steve Franklin [SMTP:steve_franklin@yahoo.com]
>         > Sent: 20 December 2001 16:14
>         > To:   powerh-l@lists.swau.edu
>         > Subject:      Axiant users
>         >
>         > I would love to hear from anyone using Axiant.  During
> development, Axiant
>         > crashes on a regular basis.  I wonder if anyone has succeeded in
>         > implementing a production Axiant application.  If you have
> succeeded I
>         > would
>         > love to know what deployment platform and database you used.  I am
> trying
>         > to
>         > use Windows 2000 with Sybase.
>         >
>         > Steve Franklin
>         > Stw Inc.
>         > Email: steve_franklin@yahoo.com
> 
> DISCLAIMER:
> This message is intended only for the use of the person(s) ("the intended
> recipients(s)") to whom it is addressed. It may contain information which is
> privileged, proprietary and/or confidential within the meaning of applicable
> law. If you are not the intended recipient, be advised that you have
> received this email in error and that any use, dissemination, forwarding,
> printing or copying of this message (including any attachments) is strictly
> prohibited.  If you have received this message in error, please contact the
> sender of this message as soon as possible.
> 
> The views or opinions expressed in this message are those of the author and
> may not necessarily be the views held by Azurgroup Limited
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe" in message body to powerh-l-request@lists.swau.edu
> http://lists.swau.edu/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.