> Wow, that looks pretty impressive.

Thanks.
> Coming from the web thing and slowly moving into the whole ERP area, I
> think I can sort of see the work in that.
> I’d be interested in your reasons to write your own application
> instead of using the Enterprise Portal that comes with Axapta, though.

Well, there’s a number of…including, but not limited to:

Performance. The ePortal is kinda slow and requires all traffic to be
handled by your production ERP server. 90%+ of our web traffic never
really needs to hit Axapta — it’s search engines, guest users, etc.,
so why burden the ERP.

Reliability. I heard Axapta’s COM Connector can get a bit bogged down
with a heavy transaction load.

Security. Mimimize the amount of un-necessary direct access to the ERP
environment where poor configuration choices could open your corporate
data and financials to the web-at-large.

Development ease. Axapta’s development environment is a great database
application IDE. It’s not a great web application IDE.

Compatibility. The ePortal really only works in IE/Window and spits
out a lot of really bad HTML. If I was going to have to do all the
work to fix that, I’d just assume do it elsewhere.

g.

> Most amazing of all,
> you made it work well in that stinky ol’ dog of a browser, Internet
> Explorer. Bravo!

If you think it’s hard to get it working in IE, try getting ASP.NET to
spit out valid X-HTML!
g.

Sean