Differences between revisions 2 and 3

Excel Integration - AH Development Notes

Contents

Development Sessions

Is there a any particular reason that statement Attribute VB_Name = "modXmlUtils" appears at the very start of the module? Can it be after the function header and CVS tag?
A user's login can expire from the server side, due to a timeout. What do we do on the client side? Should we maintain a variable contain the time that the login was last checked and then explicitly check with the server to see the user is still logged in if the time is more than x hours ago?

Exported all mod*.bas file, cleaned up the formatting and reloaded them into Lib, which I checked back into CVS.
Formatting conventions notes:
- Added header with module name, project name, CVS ID tage at the start of each module
- Added end comment at the end of each file
- Use 2-spaces for indentation
- When lines are continued, then indent to match preceding line or indent 4 spaces
Next up:
- Cleanup background colors in layout
- Fix writing of user defined fields and title columns
- Start implementing formulas

Deletions are marked like this.	Additions are marked like this.
Line 8:	Line 8:
	== 2010-03-11 == === Questions for lunchtype Skype session === 1. Is there a any particular reason that statement '''Attribute VB_Name = "modXmlUtils"''' appears at the very start of the module? Can it be after the function header and CVS tag? 1. A user's login can expire from the server side, due to a timeout. What do we do on the client side? Should we maintain a variable contain the time that the login was last checked and then explicitly check with the server to see the user is still logged in if the time is more than x hours ago? 1.