I am trying to sell a db that is for a single user and not split. What do you think?

[Micromax]

Hi I completed an accounting database for small business. I think it should work in a multi-user environment, but I have not tested it.

I want to distribute it as an .mdb or .mde. It will not be split.

Is it okay to have the user/client split the database if they so choose?

What your thoughts, I know that splitting is the best way to go, but hard to distribute.

Thanks,

Rob

 

[boblarson]

FYI:

Not splitting, even with a single user, greatly increases the chances of corruption and irrecoverable data loss.

Read this:
http://www.kallal.ca/Articles/split/index.htm

I would not distribute it as an unsplit database myself.

 

[pbaldy]

If you're looking for votes, I would also split it. You can't expect a customer to have that knowledge, and that's how it should be structured anyway. Why is it hard to distribute split? Put some relinking code in it and the customer can put the BE anywhere they want.

 

[Micromax]

Well, it looks like the votes win here. I created this db with a lot of help from access and vb mvp's. Thanks to both of you for your input. I'm planning on distributing the db via a zip folder. I know how to split the db, but sending a split db to a user would be useless. I do not know how to split and relink the db for the various access versions. The db works fine, but , my experience is very limited when it comes to giving the user a split database that requires instal on more than 1 computer with the FE and instructions on how to instal the BE to a server. I read the article, It was good. I was going to distribute Peters Software for taking care of this task, but again the user needs to know something that I have'nt even done. So much for being a complete access developer. My fault for being an accountant.

Thanks again,I appreciate your input.

 

[Micromax]

Just a quick follow up question. If I do split it for a single user and zipthe fe and be in the same folder, would that be okay for distribution?

 

[pbaldy]

Sure, though in a multi-user scenario they wouldn't (shouldn't) stay in the same folder (the BE would be in a shared folder on the network). Lots of relinking code around, including:

http://blogs.office.com/b/microsoft...atically-relink-microsoft-access-tables-.aspx

http://access.mvps.org/access/tables/tbl0009.htm

 

[Micromax]

Thanks PBaldy, I'll check out those sites. I haven't tested the db in a multi-ser environment, so I'm not sure if it will work. I assume it should. I also assume I couls split an .mde . I hope,once split,the db will work on Access 2002 and up.

Take care,
Rob

 

[pbaldy]

No problem. I'm surprised you would sell into that market without testing. I'd guess a lot of potential customers would want multiple users. As an aside, I almost always develop applications split from day one. It's a little more effort, but you never have to worry whether something will break after splitting.

 

[Micromax]

I know that I'm potentially losing for the time being. I don't know anyone who has a network to test it on. That's a tempproblemI hope. As far as you testing even during or before development, I just read that was the way to go. I wish I had known that before development. Good workon splitting before and thanks for your feedback. The truth is a friend of mine sugested I only sell to single users and I guess that's where I felt that splitting the database is somethin gthey could do easily. I set upa link on my website. Allen Browne's page on Splitting a database.

Take care,

Rob

 

[boblarson]

and I guess that's where I felt that splitting the database is somethin gthey could do easily.

Splitting isn't necessarily going to be "just do it and go." That's why I develop from the beginning with it split because it is easier to not have to deal with potential issues after splitting if you never develop with the single file format.

 

[Micromax]

That's good Bob that you also knew to develop fromthe beginning with the db split. I was just saying to pbaldy that I didn't know when I first began developing tosplit before development.

Everyhting seems to work fine on it as a monolithic db. I hope I have no problems after, but it is to late to go back.

 

[Micromax]

Gary,
If you read this here it's because I received an alert about an instant message,but didn't receive the message.
I will try to answer your questions re the selling of the Accounting db.
I'm going by memeoery here. It will be sold via the internet google and bing advertising,not direct sales.
It's now discounted at 25% off for $599 Regular price $799
There will be no support, but if they were to ask me a question within a weekof their purchase I would support these questions.
Licensing:No resale on the DB, I have a EULA. They will receive this after they purchase. BTW, there will an Open Source for the above price and non-Open Source for &399

 

[gemma-the-husky]

how can you sell something, and not support it. what if it goes wrong?

the trouble with un-split databases, is that it makes maintenance very difficult. with split data, you can just issue a new front-end that fixes the errors. you cannot do this easily with unsplit databases.

 

[Galaxiom]

Alarm bells are ringing everywhere for me on this one.

Rob, your enthusiasm is admirable but how much experience do you have as an application developer, shopkeeper and accountant?

Designing good accounting packages require a lot of knowledge in both these fields. On top of this, marketing, selling and distributing a product is not trivial.

However I see a developer who doesn't seem to comprehend the importance of splitting, a marketer who doesn't understand the importance of multiuser facilities and support.

 

[Micromax]

I'm not experienced in the programming side of things, i.e vb and some what experienced in Access. But I did make an app for accounting. The db is split, and I'm afraid of selling it exactly forthe reasons you mention in your post. I would love it if someone knew alot about the above enough to say "hey I think you may have a db that could be sold." I believe I do, but the installation and maintenance part is not that simple.

It took me about 15 years to design this database and I'm not an expert. Totally self-taught. I had the luxury of getting help when I need it from the Microsoft forums.

Anyways, I haven't made a sale yet. It may be pricey or people just don't buy an accounting database that easily.

I know for a fact that if an Access developer who is really good at what he does will find flaws in my accounting db. There won't be that many.

It works properly. This is the main thing. The user would have to enter Journal entries for month end, year end ,whenever they choose. The Reports supply info for the entries. This could be considered a drawback to some and not some others'.

It is scary, but I did spilt the db and I managed to code to relink tables.

If it works properly unsplit, I hope it will work properly split.


Thanks for your interest and honesty. I'm not sure where this is going. Would you want to have a look at the db on skydrive?

 

[bob fitz]

Thanks for your interest and honesty. I'm not sure where this is going. Would you want to have a look at the db on skydrive?

I would love to take a look at it.

 

[Micromax]

Hi Bob:

Before you clickon the link to view the db, please do not sell or giveaway the db to anyone. It is copyright.

Thanks for looking at it and not selling or giving it away.

Like to hear what you think.

Rob

 

[boblarson]

If you don't want it out there for the public, it isn't a good idea to post a link to it in the forum. PM would have been better.

 

[bob fitz]

Hi Bob:

Before you clickon the link to view the db, please do not sell or giveaway the db to anyone. It is copyright.

Thanks for looking at it and not selling or giving it away.

Like to hear what you think.

Rob

Thanks for making that available. I shall take a look at it this week end when I have more time.

 

[Micromax]

You're welcome. I'll await what your thoughts are.
Rob