Hi everyone, I need suggestions. A little corporate needs to track its data with 2-3 employees making a daily data entry/updating of few records (20-30). Data must be available to other employees. They want to store data in a SQL Server db that has been already implemented. The whole db doesn't reach 10,000 records.
They would like to implement a Web interface but they should pay someone external for this; internal resources proposed to use a shared Excel spreadsheet to be modified daily and a SQL Server job running at intervals to import Excel data.
Any problem in using Excel spreadsheets in such a scenario? Any help will be appreciated.
Thank you! Cris
cris651
0
Newbie Poster
Recommended Answers
Jump to PostI think there's no problem, it's good. If they already have the data in excel it's the easiest way to update the DB.
Couple months ago I did an web app so the user could upload the excel and import to the SQL DB.
If you are thinking of doing …
Jump to PostWhat I don't like is "shared" and "intervals". Even in small scale shared workbooks can cause user frustration and problems. Running a job at intervals reading a shared workbook, that users might be still editing - but haven't saved or have saved half-way sounds like bad idea.
May I propose …
All 5 Replies
AleMonteiro
238
Can I pick my title?
pritaeas
2,194
¯\_(ツ)_/¯
Moderator
Featured Poster
adam_k
239
Master Poster
cris651
0
Newbie Poster
adam_k
239
Master Poster
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.