I know my boss uses Quickbooks to look at reports and stuff like that. I'm not sure how relevant exchange is, nor what the significance of "terminal server is also ws r2" is. My boss wants me to write the entire system in ms access , but I feel like this will be a lot more work than simply writing it in MySQL.
Will my boss still be able to look at his reports in quickbooks if we change the database to MySQL? What would be a good database technology to use? I've been trying to learn access, and it seems that setting up a front-end and back-end database in access would be a pain in the ass.
There are going to be several sectors in the factory that will be using the client-side software to run queries and insertions into the database I think around If I can write this thing in MySQL, I think I could do the whole thing fairly pain free, but I fear that I can't because it will be incompatible with Quickbooks and the previous database Although I hear converting is fairly easy.
Mostly just Quickbook compatibility is my problem. I don't mean to be a spoil sport but there is a tremendous amount of naivety expressed in this question. It's hard to imagine that you will be successful in designing and implementing such a large system without a basic knowledge of the technologies involved. Quickbooks already covers most of the features you say you will be responsible for implementing. Are you supplementing the existing Quickbooks system, replacing it, or what?
Quickbooks uses its own extraordinarily slow database engine. SQL Server is a database. You don't use a database with it, you use it as your database. A Microsoft-centric organization such as the one you describe is not likely to be interested in installing yet another database server like MySQL. The engine can be used with other development environments and the development environment can attach to other database engines most often SQL Server, but others work too. When you say the boss wants to write the system in MS Access you need to be clear whether he means the engine, the development environment or both.
My guess is they want to use Access as the front-end development platform and SQL Server as the data store. You will not write a system of this complexity in a month. You probably won't even design it in that time. Quickbooks can use MySQL as a datasource or just about anything else , but you'll need to make your database conform to the Quickbooks way of doing things: i.
It sounds like you just need a front end data entry forms and reports and a custom back-end. Access does have its own native database, but everything gets stored in one local file and it's not good for applications that will be accessed by multiple people in multiple locations.
It also gets complicated when you need to make a change and roll it out to all of your users. That will also let you create your own tables, forms, and reports, and updates are immediate for all users, but you'll have ongoing monthly user fees.
They look great on a resume, though! Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more.
Asked 9 years, 9 months ago. Active 9 years, 9 months ago. Viewed 2k times. The guy who runs the server sent me this too: "We also have quickbooks installed on the server and we have Exchange running. Quantity, 0.
How to store the above query result in new table? Use Full outer Join to display all the matched and non matched output select p. Behzad 3, 4 4 gold badges 34 34 silver badges 61 61 bronze badges.
Quantity AS Expr1, p. Tharif Tharif Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped.
Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback?
0コメント