Bento was Apple/FileMaker's consumer database product that was discontinued in 2013. Its performance has degraded with each successive release of MacOS, but my wife has continued to use it on her MacBook Pro, up through MacOS 10.9.5. Today, all of her records vanished from with the Bento interface.
In trying to find them, I researched the default location for the Bento database, and found that it is supposedly in Home>Library>Application Support>Bento>bento.bentodb. However, looking at the file in that location on her computer shows a 1mb file that was last updated in 2013. Checking Time Machine backups for several months shows the same file, same date, same size in that location. Which doesn't make any sense, as she uses the application (and thus the database) every day.
I did a standard Finder search for the filename, and found only that one instance. But logic tells me that there MUST be another database, somewhere on the disk, that is the one actually being used. But I have no idea where or how to find it. Help?!
The location is right. That's where the Bento database is by default and you don't seem to have changed it.
Have you tried importing it to FileMaker 10,11, or 12? These versions can import Bento data directly.
Alternatively, the Bento Migration Tool can convert your Bento data to FileMaker tables in the .fmp12 format, which can be opened by all versions from 12-16.
More here.
Related
I have a setup where I have one computer at the office and another at my house, and the project data are being shared via OneDrive. This is purely for my own convenience and I only ever work on one computer at a time, shutting down Visual Studio when I'm not using it on either computer.
My current problem involves a project that is being synchronised via OneDrive but uses a SQL Server LocalDB database for development and testing but, despite the files being synchronised between the two computers, data that was inserted on one computer does not appear in queries run on the second computer.
Synchronisation only occurs once Visual Studio is shut down, since file locking prevents the process. I have verified that both the .mdf and the .ldf files are being copied (the file sizes and modification dates are correct). I have also physically copied the files via external harddrive to rule out the OneDrive synchronisation step, but the problem persists.
I have also verified that even after the files are copied, the inserted data is still present on the computer where the INSERT was done, but is not appearing when doing a SELECT on the second computer.
I was under the impression that LocalDB only used the .mdf and .ldf files, are there caching files somewhere else that I also need to synchronise?
All code and other project files are being synchronised just fine, it's only the database that is experiencing this problem.
I understand that this is probably a weird setup for most people, and I would never do this if I were in a team setting but I would appreciate some insight into what could be going wrong.
Sorry for the trouble to anyone, I seem to have solved the issue myself.
Just for pure sanity, I tried to detach and then re-attach the .mdf file on the second computer (the one that was not picking up the INSERTed data) and got an error about the LocalDB instance being a version too old for the file.
Turns out the computer on which the INSERTs were done was running a v13 instance and upgraded the .mdf file to that version, while the other computer was running a v11 instance. Both computers are now running on the same instance version and the missing data is now showing.
Apologies if this has come up before - I have spend the entire day Googling this and have gotten no closer to working out what to do.
We have a database that we purchased from a 3rd party. This was first received years ago - long before I ever worked here. The person that previously set it up no longer works here so I can't ask them what they did and I can't find any documentation of the process that they used.
We have just received an update from the 3rd party however it wasn't really what I expected. I was lead to believe that it was going to be a bunch of csv files however it appears to be a database dump from a different system.
The received update contains a .mdf and a .ldf file as well as a couple of csv files. From what I can tell from online, .mdf and .ldf files are produced using SQL Server. I do not have any access to SQL Server and only use PostgreSQL.
I am just wondering if there is any way to import the .mdf and .ldf files into PostgreSQL? I am on OS X (El Capitan).
The only similar post I could find was:
https://dba.stackexchange.com/questions/17835/how-to-convert-sql-server-mdf-database-to-mac-os-postgresql-database-on-mac-os
However the suggested answers seemed to require using SQL Server - which I don't have any access to.
I also looked at:
https://wiki.postgresql.org/wiki/Converting_from_other_Databases_to_PostgreSQL
However I'll be honest - I got pretty confused pretty quickly and a lot of them seemed to be Windows specific tools and I need Mac. (Or they are way too expensive!)
Has any one got any suggestions as I am completely stuck?
I have a .FDB Firebird file from an commercial Application we don't use anymore. It contains my customer data an I want to export or access it in some manner.
I have seen many procedures that require Firebird server installation, JDBC, ODBC drivers, GUI (I tried RazorSQL) tools that are just to complex for me to handle. I have been hitting into one problem or another every time, solve point by point but still hitting the wall.
Does anyone have a quick and easy way to simply open it (preferably on Mac OSX)? One that a non-Firebird / database tech guy can actually follow?
I finally found what was the issue.
It turns out that the path file to the .FBD file was the culprit. Mine had Portuguese accented words on the folder name. It seems like isql does not accept it. I moved the file to Desktop and the following command worked fine.
SQL> CONNECT /Users/user_name/Desktop/db_name.FDB;
Still haven't been able to use any Razorsql Gui tool though. It seems to have an issue with the JDBC driver.
My apartment burned down a few days ago and my beloved MacBook Pro was one of the many electronic casualties. While I of course back up (using Time Machine) and my backup drive managed to survive, much to my dismay many of the most important files seem to be missing from my Time Machine backups. Namely, all of my recent XCode projects. In fact, the entire directory (titled "Re-Programming") which housed all of my development projects is inexplicably missing from my latest backups.
Curiously, it seems that some of my older backups do contain the missing folder (May 10 has the folder, while May 19 through the latest do not).
I would have wanted to try Migration Assistant to bring my files over to a friend's computer but I'm unable to because my backups were made in Lion and he is using Snow Leopard. I'm fairly certain it wouldn't help though (not only is the directory missing, but a search for certain header files I remember the filename of don't show up in Search).
I've done some googling and it seems Time Machine does not backup XCode build folders to save space. This makes sense as it would take up a lot of space and are easily recreated by building your projects. But why on earth would Time Machine not backup my oh-so-important XCode project files?
The plot thickens though. Even if, for some strange reason Time Machine has a bug that prevents it from backing up XCode projects, what about other projects? I had some Android projects in there too, maybe even some old HTML/CSS/PHP happenings. What happened to those, and why the ENTIRE directory, not just the XCode projects? And why did it USED TO backup my most important directory and suddenly stopped without my knowledge back in May?
Am I missing something here? Perhaps they were placed in a weird place that isn't obvious to me? Any help is appreciated.
Sorry to hear that. I believe TimeMachine backups are just a .sparsebundle files. You should be able to mount the file directly and browse through it to see if you can find any of your project files.
https://superuser.com/questions/147998/backing-up-my-xcode-projects
I am not sure about Time Machine but here are some alternatives!
So I did something really stupid... I got a new MBP, and gave my old one to a friend. Before I did that, I transferred all of the contents of my big folders (Documents, Downloads, etc...) to my new Mac, and then I deleted the user on my old Mac. Unfortunately, I neglected to transfer the folder that contained the entire Xcode Project for my app that is currently on the App Store, as it wasn't in one of those folders, and I'm the only one who had it. The only way of being able to retrieve it that I thought of was that since I had to upload the binary to iTunes Connect to submit the app, Apple might still have it. Otherwise, I guess I'll have to completely start from scratch if I ever want to update it again. I just contacted Apple via iTunes Connect, but I was wondering if anyone has any idea of what I am able to do now, mainly, if Apple will actually give me all the files back. Thanks.
Any chance you've got a backup via timemachine?
Timemachine can't help you in the case of a fire (see http://github.com for what you can do about fires, hurricanes, tornadoes, volcanoes, or thieves), but maybe it can save your bacon right now. :)
Yeah, you pretty much lost it. I'd recommend looking at some source control - for example Github. It's built into XCode, and Github is pretty cheap for Private Repositories, and free for public ones.
You (nor Apple) won't be able to retrieve it from the binary.
No revision control system?!
You wiped your data or only simply deleted?
Because, here is a possibility retrieve data from the HDD (or at least some parts) when only simply deleted them. Delete usually does not wipe the data.
If you can get your old HDD, you should:
- insert it into external usb-HDD enclosure
- attach to your new MAC
- make an image from it to one big file (with the command "dd") (assuming than your new HDD is bigger than your old)
- and with several tools you can "try" recover some data
every use of the old HDD drastically lowering the chance recovering something from it.