KISS MY ASS MICKEYSOFT!!!
Robert wrote in message <355C47C8...@sisconet.com>...
<snip>
One would think that such a literate and reasonable fellow would read the
help file or at least look at the tools available.
One would suspect that maybe someone asked him to do a job and he couldn't
solve such a simple task.
Robert <rwma...@sisconet.com> wrote in article
<355C47C8...@sisconet.com>...
Isn't it nice when the ignorant and rude decide it's time to mouth off.
Robert wrote in message <355C47C8...@sisconet.com>...
[Message Cut to protect the innocent] ...
(From online Helfp) Split an existing database between its data and its
objects
This procedure splits a database into two files: one that contains the
tables and one that contains the queries, forms, reports, macros, and
modules. This way, users who need to access the data can customize their
own forms, reports, and other objects while maintaining a single source of
data on the network.
1 On the Tools menu, point to Add-ins, and then click Database Splitter.
2 Follow the instructions in the Database Splitter Wizard dialog boxes.
--
Doug McKinley
Robert <rwma...@sisconet.com> wrote in article
<355C47C8...@sisconet.com>...
> Microsoft Access is the biggest piece of shit. If you are considering
> using any version of Microsoft Access to create any decent application,
> you are out of your mind. The implimentation of Visual Basic within
> Access is a joke. Anyone who is experienced in using any version of VB
> will notice that there was almost no collaboration between projects when
> they were in development. Access Basic is basically is big fuck up of VB
> and you can't do in Access Basic what you can in Visual Basic. Also,
> another idiotic idea that Microsoft had was to integrate all of the
> forms, code, reports, tables, etc. etc. into one file. THIS MEANS THAT
> WHEN YOU WANT TO UPDATE THE PROGRAM THE DATABASE MUST BE REPLACED!!!
> What this means to the programmer is that whenever you want to update a
> customers program with the latest and greatest, you must first find a
> way to export all of the data from the old database into the new one.
> THERE IS NO SEPERATION OF CODE AND DATA! This is a fundamental that is
> taught at the lowest level in any computer science or engineering
If you at a level above moron you would have figured out that to prevent
this problem the Data is always kept in a separate .mbd from the program.
This totally eliminate this problem. As for the VB in Access. That doesn't
exist so to say. It's called VBA!!!! Visual Basic for Applications. Once
Again If you had a fuckin clue you would realize the power now available to
interact with any other Application that uses VBA
(Outlook,Schedule++,Word,Excel,PowerPoint,Project etc.)
Maybe you should stick to you Visual Basic NewsGroups where maybe, if we're
lucky you might have some level of intelligence.
fjm
Terry Kreft wrote in message
<#Bo1CyBg...@uppssnewspub05.moswest.msn.net>...
- Rebecca
Frank Murray wrote in message ...
What I meant was that the original poster was ignorant in that he obviously
doesn't understand Access and rude in the way that he phrased his ignorant
message.
Rebecca Riordan wrote in message ...
>Good lord, I hope you're right...software having opinions of _us_? Keep a
>body up at night, that would...
>
> - Rebecca
>
- Rebecca.
Terry Kreft wrote in message ...
THIS MEANS THAT
>>>WHEN YOU WANT TO UPDATE THE PROGRAM THE DATABASE MUST BE REPLACED!!!
>>>What this means to the programmer is that whenever you want to update a
>>>customers program with the latest and greatest, you must first find a
>>>way to export all of the data from the old database into the new one.
I think he means that if you create a new form, you cannot send the
user the form by itself, as you can in VB, as forms are files with the
.frm extension.
One thing that you could do is create your new form, create a blank
database, import that new form into the blank database, then send the
user the new database containing the one form, then tell them to open
there database and import the new form...... sheesh
sheesh, meaning this sounds like a lot of work
>>>
>>>
>>>
>>>
I could understand your response if you were defending the originators
views, although I would not agree with that, but to defend the way in which
they were expressed I find quite astounding.
Chris wrote in message <356acb51...@newsserver.epix.net>...
>>>>>>>What this means to the programmer is that whenever you want to update
a
>>>>>>>customers program with the latest and greatest, you must first find a
>>>>>>>way to export all of the data from the old database into the new one.
The original poster clearly states here that they are talking about
exporting and importing data, not about forms, they clearly do not
understand about splitting the database.
Unfortunately your further statements also show your own ignorance on the
matter, in VB you do not send people .frm files you send an updated
executable, in Access you do not send people a database with the extra forms
in, you send a replacement frontend which they then copy into place and use
with there existing data. No Sheesh about it, simple and straightforward.
Chris wrote in message <356acad5...@newsserver.epix.net>...
WARNING::::::::>
Some times you may need gray matter to Figure them out. YOU
PUTZ!!!!!
Robert wrote:
Microsoft Access is the biggest piece of shit. If you are considering
using any version of Microsoft Access to create any decent application,
you are out of your mind. The implimentation of Visual Basic within
Access is a joke. Anyone who is experienced in using any version of VB
will notice that there was almost no collaboration between projects when
they were in development. Access Basic is basically is big fuck up of VB
and you can't do in Access Basic what you can in Visual Basic. Also,
another idiotic idea that Microsoft had was to integrate all of the
forms, code, reports, tables, etc. etc. into one file. THIS MEANS THAT
WHEN YOU WANT TO UPDATE THE PROGRAM THE DATABASE MUST BE REPLACED!!!
What this means to the programmer is that whenever you want to update a
customers program with the latest and greatest, you must first find a
way to export all of the data from the old database into the new one.
>>>Chris,
>>>Before you go around defending the undefendable try reading what they say,
>>not putting your intertpretation on what they say.
This is an NG. We have no choice but to interpret what we read which
lends itself to misinterpretation.
>>>
>>>>>>>>>>What this means to the programmer is that whenever you want to update
>>>a
>>>>>>>>>>customers program with the latest and greatest, you must first find a
>>>>>>>>>>way to export all of the data from the old database into the new one.
>>>
>>>The original poster clearly states here that they are talking about
>>>exporting and importing data, not about forms, they clearly do not
>>>understand about splitting the database.
>>>
>>>Unfortunately
It's not unfortunate at all. I'm ignorant about a lot of things and
don't feel the least bit ashamed of it.
your further statements also show your own ignorance on the
>>>matter, in VB you do not send people .frm files you send an updated
>>>executable,
Not always necessarily the case.
Before YOU go around pontificating, realize that your experience with
a particular piece of software is not everyone elses.
in Access you do not send people a database with the extra forms
>>>in, you send a replacement frontend which they then copy into place and use
>>>with there existing data. No Sheesh about it, simple and straightforward.
Thanks for the info.
Now why couldn't you have relayed this info to the original poster so
that he or she could reconsider???
You did nothing but complain about his or her language and then began
to harp on me because I saw some validity in what he or she was
saying.
>>>Chris wrote in message <356acad5...@newsserver.epix.net>...
>>>>On Tue, 26 May 1998 13:57:32 GMT, ch...@epix.net (Chris) wrote:
>>>>
>>>>>>>On Fri, 15 May 1998 09:48:56 -0400, Robert <rwma...@sisconet.com>
>>>>>>>wrote:
>>>>>>>
>>>>>>> THIS MEANS THAT
>>>>>>>>>>WHEN YOU WANT TO UPDATE THE PROGRAM THE DATABASE MUST BE REPLACED!!!
>>>>>>>>>>What this means to the programmer is that whenever you want to update
>>>a
>>>>>>>>>>customers program with the latest and greatest, you must first find a
>>>>>>>>>>way to export all of the data from the old database into the new one.
>>>>>>>
>>>>>>>
>>>Well Chris,
>>>You have a strange idea of what is meant by rude. IMO someone who rants,
>>>raves and curses with no apparent control is extremely rude the, to my mind,
>>>gentle responses to this behaviour from the other respondents in this thread
>>>I find quite extraordinary.
>>>
>>>I could understand your response if you were defending the originators
>>>views,
The poster's views and the way in which they were expressed are
seperate issues.
although I would not agree with that, but to defend the way in which
>>>they were expressed I find quite astounding.
Didn't defend them. I simply stated that I didn't see anything rude
except for some of the responses to them.
1) You did not read the original message properly.
2) I believe taht if people want to discuss things they should do so in
a reasonable manner not swearing and cursing simply because they don't
understand what they are doing.
3) I have wasted enough time talking about the same subject from
opposite points of view with you.
Chris wrote in message <3575d0c1...@newsserver.epix.net>...