hello everyone ... i have a client who is looking to introduce pocket pc's into there world ... they are going to purchase one for me to play with ... any suggestions on which model is best from a programming perspective? ... any good books or websites (besides microsoft's) for code examples? ... i will be using vs2003 and c# thanks

hi guys ... i get this error when i put the following code in the application_onStart event of the globals.asa file ... the set application("objWORK_QUEUE_XSLT") = objXslt line causes the error ... anyone know the problem? ERROR: Response object, ASP 0185 (0x80020003) A default property was not found for the object. CODE: 'cache xslts dim objXslDoc dim strFilePath dim objXslt set objXslDoc = createObject("Msxml2.FreeThreadedDOMDocument.4.0") objXslDoc.async = false strFilePath = server.mapPath("..\..\xml\workQueue.xslt") objXslDoc.load strFilePath set objXslt = createObject("Msxml2.XSLTemplate.4.0") objXslt.stylesheet = objXslDoc set application("objWORK_QUEUE_XSLT") = objXslt

our environment includes a very large oracle database which we use microsoft technologies to access (ado, oo4o, .net oracle provider) ... we want to wrap oracle so all applications must access it through our data service layer (mainly to isolate them from oracle changes) ... as far as business rules, corporate business rules will be included in our data services, but application specific data rules will be outside the data services the following diagram outlines (in a very simple way) two approached we were discussing http://www.lejuan5150.com/lejuan5150/media/dataAccessTier.jpg[^] hope this clears things up a bit ... thanks for your time

in my company i am responsible for creating a data service layer so no applications access our oracle database directly (they must either soap or dcom to our data services) ... our major point of conflict when designing this layer is whether most of the logic should be in the database (pl/sql packages), or in the com+ components ... the "oracle guys" think oracle should do all the work, and the com+ components should be very simple ... i personally think the opposite, move most of the logic to the com+ components what would your opinion be? thanks, john

oooo ... that is pretty

hi there ... my team is looking for a simple web application to track projects/tasks/resources/time ... we could build one, but i thought i would check for a free/cheap one first ... it would have to be asp or asp.net based (com components are ok), and preferably have a ms access database ... any suggestions? thanks, john

thanks ... excellent article

ooops ... the image didn't show up ... here is a link ... http://www.lejuan5150.com/lejuan5150/media/dataaccesstier.jpg[^]

hi there ... i am new to these forums (this is my first post) ... i am hoping you guys could help me make an architectural decision on how to implement a data access tier ... here is the situation: - we have a large oracle database (thousands of tables) - we want to isolate applications from database changes - applications can access the data access tier via soap or dcom our team came up with two options diagrammed below ... essentially, option 1 is creating a representation of the database in xml using oracle stored procedures, with a simple com+ component for client access ... option 2 is creating an object hierarchy in com+ that represents the database ... the hierarchy can be accessed directly or be converted to xml. any opinions on which option is better? thanks, john