is it possible to access meta data from a Microsoft mdb? We have many mdb files and would like to know which files are used in each. Is this data accessible programmatically or with special utility?
Related
Scenario: I have an IBM Domino web application (.NSF) and contains divisions (refer to the image). I want to migrate the content (such as blogs, main content and the article) to my WebSphere Portal. What is the first thing to do?
My understanding in migration is database to database migration and seems I don't know where to find the database for my contents knowing that database in creating domino application is built in. Advance thanks!
Refer to this image: http://postimg.org/image/irxsjdk8p/
The database is the NSF file - although it's possible that the information might be aggregated from several NSF files so you'll have to do some analysis. The first thing to do is to use the Notes client to identify the documents that contain the content that you want to migrate, check their properties to determine what NSF file they are stored in and what form they are based on, and then use Domino Designer to open the NSF file (or files, possibly) and analyze the form and determine which items contain the values that need to be migrated.
Good Afternoon,
I am in the process of developing in vb.net a simple “cheque printing” application which will allow users to fill in a few text boxes with the values that will be printed on a cheque.
When they hit the print button, the values will be sent to the printer, but I also want the values they input in the text boxes saved to a file, so like a history file of all the cheques that were created.
I am thinking to use either an access database or an excel spreadsheet as my history file, but I am not quite sure on which would be best.
Please note that in my environment storing this information in a SQL database is not an option and also this file will most likely be stored/accessed from the network.
The history file needs to be:
1.Stable (cannot corrupt easy)
2.Reliable
3.Easily exportable in case we need to export the information to one of our in-house systems.
4.editable from the application I am developing
Kindly advise,
A
XML. Save the data to DataTable object and then use the .WriteXML method to save it as an xml file. I'd advise creating a strongly-typed DataTable class for this, so that the XML can be exported with a reliable schema and imported easily.
If you are using different fonts, you could use a .rtf (rich text format) which will save the format of the text that you send to print... it is a universal file format, you can open it with open office, ms office, or any office suite you have...
Access will be best choice,
it's relational database and can make a form from this file to do what are you looking for without VB or any code.
Also you can access this file from network.
for more detail about setting for this file go to this link
http://goo.gl/bOfGp6
and you will find more options complete your work.
I would use a MySQL server. It's free.
XML is also good, but I hate sharing folders...
I've read that the attachment data type in MS Access should only be used if the database will be use within SharePoint.
Could someone recommend an alternative to this data type? I'm developing a database for users to submit entries and they would like the option to attach notes/pictures with some of the entries.
Generally, I find that storing a path to the file you want to attach is the best option, if it is viable.
If they are images, the image control now has a ControlSource property, so you can bind it to a field in the table that contains the path.
I am making a small application that will read .csv files into a newly generated access table (generated with vb.net), I am filling this database with sql and now I would like to output that table as a .dbf file!
I can't find any info on this subject.
I know some of you will tell me to just make the script in vba in access, but there are some functions that require me to use vb.net and the client wants a single .exe file.
There is a forum post here that includes some VB.NET sample code to create a .dbf file and write some data into it. The code uses the Visual FoxPro OLEDB driver (VFPOLEDB) which is no longer distributed with Windows by default, but can be downloaded here.
I have a stand-alone Windows Form app written in VB.NET that currently connects to a local Access DB (.mdb file) and consumes data from several of the tables. It never writes to nor modifies the DB. I'm trying to figure out how to secure this DB so the user has no access to it. I'm thinking the best way is to store the DB as an embedded resource within the project. However, I can't figure out how to make this work.
I've added the .mdb file to the project resources and set its properties to "Embedded Resource" and "Do not copy." But now how do I reference the DB to create the connection?
Before I used the connection string "Provider=Microsoft.Jet.OLEDB.4.0; Data Source=MyDatabase.mdb"
How do I write the connection string now with reference to an embedded resource?
"I'm thinking the best way is to store the DB as an embedded resource within the project."
This usually relates to old skool security, in the olden days DotNetNuke developers that used Access dBs as their backend actually renamed the .mdb to .resources as you cant download a resource file from the web.
"Would it be better to export the DB to xml or something like that and then use a stream reader as opposed to a database connection?"
No. You cant read an Access file from a stream And an XML dB has even less concurrency support than an Access Database.
If you really need to protect the data, then you've absolutely chosen the wrong data store.
#JohnBustos wrote "Store the DB remotely and have the program access it over the internet."
Please do not do this. If anything put it on a network share and restrict access. Then look at upgrading the access dB to SQL Server.
Yes, I have had the same problem and I converted the database into a XML or even a TXT file that is embedded. It works very fine !
Sorry, I never closed this out.
My solution was even simpler than those proposed. You can add the .mdb file to the project itself and not mess with the whole "Resource" business. Then set the file's Copy to Output property to "Do not copy". So the .mdb gets compiled into the app, but file itself is not available to the user.