I'd actually consider it, but that pay rate isn't that much more take-home than what I'm making now.
Tho I wonder, if I arranged to still live in Ohio but work in New York state, how that tax situation works out?
If you set foot in NY, NY says that your taxes go to NY. Even if you only touch it while commuting to work and not actually doing the work there.
So, according to how NY does things, if I drive to Main in order to do some consulting work. I'd owe taxes on that to Ohio, Pennsylvania, New York, Connecticut, Massachusetts, New Hampshire, and Maine..... that would be over 100% of net. wtf!
Yes, but only NY does that. It's a major issues for truckers who pass through the state and owe taxes for every day that they were on the soil even just for a minute.
I'm guessing they only bother people without the money to fight back? Because that is the exact scenario that caused The Articles of Confederation to utterly fail.
Same policy, basically, that the fed uses. So good luck fighting it.
Good old Merica. I need to find a fiddle and a roof.
Not surprising. SharePoint on Office365 is slightly different then the one locally hosted (from my limited experience) It can be a powerful tool if they are building an app to facilitate or replace file sharing. But if they just want to use it for a glorified WebDav repository then there are other tools that would work better.
Any reason OneDrive for Business wouldn't work for them? Or will there be ownership issues if they go through that process?
Owner Ship issues is what they seem to think. Like I said they just really need someone that really knows SharePoint well to help them get it setup. A Developer is what they asked for but....
Yes, and it is what YOU asked for in turn, knowing that if you deliver that, it will be a big failure. That's my point. If you know that they asked for the wrong thing, you have to manage that. Repeating bad information will just lead to getting the wrong resource.
@Dashrender the problem with using an actual database like MySQL/MariaDB/SQL Express is that you then have to write an interface to even look at the data. For simple data, it is much easier to simply use the GUI that Access/Base provides to look at records.
That's mostly true. If the data is flat or flat-ish, though, standard free tools like myPhpAdmin will give you a GUI without any extra effort. It's not technically included in the base package, but is so standard that many people think of it that way. But definitely would not require writing your own interface if the data did not need to be reassembled in a relational way.