Member Avatar for apchidara

hi every one
I have lots of excel tables which I need to fech specific data from them and show it on my form so that the user can choose them and I need to record the user's choices in one excel file.
how do u think I should explore the data(choices)to the user?
(combobox,data grid,.....????????????????????)
please help me
thanks

  • 4 Contributors
  • 3 Replies
  • 117 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by binoj_daniel

Dani AI

Generated

A practical way to move this thread forward is to separate two decisions: how users browse and pick rows, and where/ how those picks are recorded. needs to start by answering four simple questions: how many rows per sheet, how many columns matter to the user, does the user pick one item or many, and how frequently will the Excel source change? is right that the UI is a design choice — the checklist below turns that choice into concrete tradeoffs.

For the browser UI, use patterns that match scale and selection mode:

  • Small lists: an autocomplete-enabled single-select control (fast for users).
  • Multi-column records (search/sort needed): a paged/virtualized grid with a selectable row or a checkbox column so users can preview full records.
  • Large datasets: server-side filtering and incremental search (AJAX typeahead), not a giant dropdown.
    Add clear preview/confirmation of selections and support export of chosen rows.

For persistence, avoid having every user write back into the original Excel files. Treat Excel as an import/export format: import sheets into a normalized table or document store and record user choices as rows with userID, itemID and timestamp. This removes Excel locking/concurrency problems and makes queries and reporting reliable. When you need to generate an Excel report, use a library rather than automating Excel on the server (see EPPlus or the Open XML SDK for programmatic export).

Practical pitfalls and quick tips: validate column headers and types when importing (dates and empty cells are common issues), map columns explicitly instead of relying on position, use parameterized writes and transactions when saving choices, and prototype with a realistic data sample so response times and multi-select UX can be tuned before rollout. This keeps the UI responsive and the recording of choices robust and auditable, building on points raised by and .

Recommended Answers

All 3 Replies

Member Avatar for Hamrick

It depends on how much data you have and how users expect it to be presented... That's a design thing that's up to you.

Member Avatar for preetham.saroja

hai,
To perform has u said-1)fetch the data from one table& display it on the form using -dropdownlist, 2)then based on his/her selection (or user clicked)just display it on other table thats it...
1)select * from table where ID=" & id.txt
2)insert into table2 where ID =" &id.selectedvalue
happy coding....

Member Avatar for binoj_daniel

Again! its a personal choice representing data. You have different options to choose from to design the interface. To provide list options to the user to can use listbox, combobox, listview, checkboxes or radio buttons depending upon the situation and need.

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.