Member Avatar for silvercats
  • 2 Contributors
  • 1 Reply
  • 81 Views
  • 3 Hours Discussion Span
  • Latest Post Latest Post by tinstaafl
Member Avatar for tinstaafl

the diagram doesn't seem too bad. I would offer a suggestion. To make item and invoice separate classes then in your invoice class make a list of item a property and in the main class a list of invoice as a property. This allows you to leverage the built-in and extended methods of the list class for searches, sorting, replacing, deleting, etc.. This also has the advantage os implifying your code as item and invoice only need to be coded once.

Edited by tinstaafl
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.