deedub84
asked on
Program Data Storage
Hi Experts,
I'm new to C#; my experience is primarily with Access VBA.
I have developed an end-user application in Access that may be marketable. Ideally this application would be 'stand-alone' and not an access mde etc, which would require users to own Access. What I'm having a hard time understanding is how might a program be designed in C# which would not require a back-end data store such as sql server, access, etc. which would seemingly add to the cost.
So the question is, what is the best way to store 'user' information -- the data of the program -- in a program developed in C#; also I'd welcome suggestions about any reference books that would cover this topic.
Thanks,
deedub84
I'm new to C#; my experience is primarily with Access VBA.
I have developed an end-user application in Access that may be marketable. Ideally this application would be 'stand-alone' and not an access mde etc, which would require users to own Access. What I'm having a hard time understanding is how might a program be designed in C# which would not require a back-end data store such as sql server, access, etc. which would seemingly add to the cost.
So the question is, what is the best way to store 'user' information -- the data of the program -- in a program developed in C#; also I'd welcome suggestions about any reference books that would cover this topic.
Thanks,
deedub84
You can store it how you like is the real answer here. Flat file may be an option (ie, serialised objects persisted to file) or maybe XML. It depends what you want from the application. Do you need database type functionality? Indexed retrieval of data? Referential integrity?
ASKER
Having cut my teeth in the access / sql server world; I'm tempted to say database type functionality. But the application really is straightforward. I have a couple of tables that store the data in the Access version. There is some user selection of certain lines for printing. Probably the biggest need is some of the data (and therefore probably all) the data would need to be secured in the sense I wouldn't want anyone just to be able to open up the data and be able to read it. The application is more along the lines of a mini app versus something with full functionality.
Ultimately, I'm so new to this part of the programming world, some pointers to good references or primers (if they exist!) would be great.
Ultimately, I'm so new to this part of the programming world, some pointers to good references or primers (if they exist!) would be great.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.