learn sql then
err why would export damage data? Can you create a new db? Export from folemaker to filemaker should be less problematic. Unless all they are looking for is data entry clerk :biggrin:
Sounds like a good investment of time compared to neffing.... maybe :hmm:
Honestly, I think their entire intent is to have me as a data entry clerk. It probably hasn't occurred to them that this whole thing can short cut with some other activities.
I don't know why the export damaged data, but I know when I opened the exported file, there were a lot of weird character strings that didn't belong there, additional characters appended to values, et cetera. Maybe importing back into FMP would clean those out, I don't know.
I doubt I can create a new DB on their server, but I might be able to create a new DB on the local machine I'm working on, and if I can get that... oh, right. They're going to give me basically old.db and new.db and say get the data from old into new. The new one will be structured how they want... so if I could duplicate it over to here and work on it locally? I dunno.
see if that can be done. One bad thing is it will reduce billable hours
I'm not on billable hours. I'm on a fixed 8-5-ish schedule. So if it saves me effort, it's a win.
I'm not on billable hours. I'm on a fixed 8-5-ish schedule. So if it saves me effort, it's a win.
Can't you play Minecraft at work? great time sink.I am obviously just jealous :|
Can't you play Minecraft at work? great time sink.
Can you plug it into Excel, massage it, and then import it into Filemaker?
I'm not on billable hours. I'm on a fixed 8-5-ish schedule. So if it saves me effort, it's a win.
apparently export wrecks the data, may have binaries in there.