Group:  Microsoft Access ยป microsoft.public.access.dataaccess.pages
Thread: Not able to create a DAP from unbound form.

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

Not able to create a DAP from unbound form.
ChasAA 08.09.2006 13:25:02
Hello All,
I am new to Access although a fairly experienced VBA developer. I have
recently had Access Loaded onto my set. I am in the process of developing a
small application that has three main forms.

1) Sign in Form
2) A form that asks user for input and process a few tables
3) The main form, this form leads to various processing of tables.

The text boxes in all the forms are unbound as I populate the text boxes
with the neccessary information. (This info is from Tables).

I want this application to be run from our Intranet. The first problem is
that I cannot save the forms as DAP. I keep getting the message that unbound
Forms cannot be converted to XML (or some similar response).

Am I understanding this message correctly, is this because my forms' text
boxes do not have a Source (showing "unbound" in Design View?, I do not need
them to have a source).

Is there a way around this. I chose this approach as all users do not have
Access on their sets.

Thanks in advance for any suggestions.

Chas
Re: Not able to create a DAP from unbound form.
"Ken Snell \(MVP\)" <kthsneisllis9[ at ]ncoomcastt.renaetl> 08.09.2006 16:06:19
I eschew using the wizard in ACCESS to convert a form to a DAP because DAPs
are so different from forms that it's almost never successful at making a
usable DAP. In your case, I recommend that you build the DAP from scratch.

However, let me caution you -- DAPs are significantly different from forms,
and things that work in forms usually don't work in DAPs. Also, DAPs use
VBScript, not VBA.

--

Ken Snell
<MS ACCESS MVP>


"ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
news:2B85A37C-4885-455D-B047-BF82BDB472AD[ at ]microsoft.com...
[Quoted Text]
> Hello All,
> I am new to Access although a fairly experienced VBA developer. I have
> recently had Access Loaded onto my set. I am in the process of developing
> a
> small application that has three main forms.
>
> 1) Sign in Form
> 2) A form that asks user for input and process a few tables
> 3) The main form, this form leads to various processing of tables.
>
> The text boxes in all the forms are unbound as I populate the text boxes
> with the neccessary information. (This info is from Tables).
>
> I want this application to be run from our Intranet. The first problem is
> that I cannot save the forms as DAP. I keep getting the message that
> unbound
> Forms cannot be converted to XML (or some similar response).
>
> Am I understanding this message correctly, is this because my forms' text
> boxes do not have a Source (showing "unbound" in Design View?, I do not
> need
> them to have a source).
>
> Is there a way around this. I chose this approach as all users do not
> have
> Access on their sets.
>
> Thanks in advance for any suggestions.
>
> Chas


Re: Not able to create a DAP from unbound form.
ChasAA 09.09.2006 07:48:04
Ken
Thanks for the prompt reply. I will try and create a simple DAP from scratch.
The only reason I was looking athe DAP approach was that not all users will
have Access.

Is there any other way that I can have an application on the company
Intranet, Shared drive or Internet so that users without Access can use it.

Thanks

Chas


"Ken Snell (MVP)" wrote:

[Quoted Text]
> I eschew using the wizard in ACCESS to convert a form to a DAP because DAPs
> are so different from forms that it's almost never successful at making a
> usable DAP. In your case, I recommend that you build the DAP from scratch.
>
> However, let me caution you -- DAPs are significantly different from forms,
> and things that work in forms usually don't work in DAPs. Also, DAPs use
> VBScript, not VBA.
>
> --
>
> Ken Snell
> <MS ACCESS MVP>
>
>
> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
> news:2B85A37C-4885-455D-B047-BF82BDB472AD[ at ]microsoft.com...
> > Hello All,
> > I am new to Access although a fairly experienced VBA developer. I have
> > recently had Access Loaded onto my set. I am in the process of developing
> > a
> > small application that has three main forms.
> >
> > 1) Sign in Form
> > 2) A form that asks user for input and process a few tables
> > 3) The main form, this form leads to various processing of tables.
> >
> > The text boxes in all the forms are unbound as I populate the text boxes
> > with the neccessary information. (This info is from Tables).
> >
> > I want this application to be run from our Intranet. The first problem is
> > that I cannot save the forms as DAP. I keep getting the message that
> > unbound
> > Forms cannot be converted to XML (or some similar response).
> >
> > Am I understanding this message correctly, is this because my forms' text
> > boxes do not have a Source (showing "unbound" in Design View?, I do not
> > need
> > them to have a source).
> >
> > Is there a way around this. I chose this approach as all users do not
> > have
> > Access on their sets.
> >
> > Thanks in advance for any suggestions.
> >
> > Chas
>
>
>
Re: Not able to create a DAP from unbound form.
"Ken Snell \(MVP\)" <kthsneisllis9[ at ]ncoomcastt.renaetl> 09.09.2006 16:12:34
There is a runtime option for ACCESS that allows a person who has the
license to create them the ability to create ACCESS applications that can be
run by uses who don't have ACCESS installed on their PCs. This is not a part
of the regular ACCESS software though, and must be purchased separately.
What you need to purchase depends upon which version of ACCESS you would use
to generate the runtime setup. Then you install the runtimes on each
person's PCs.

Otherwise, DAPs and ASPs (active server pages, using Internet Explorer)
would be the methods for allowing use of ACCESS database by people who don't
have ACCESS. Note that the users must have the Office Web Components
installed on their PCs in order to use DAPs.
--

Ken Snell
<MS ACCESS MVP>




"ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
news:AC626855-A0EA-4E9D-80E9-B3B2C9D1D7B0[ at ]microsoft.com...
[Quoted Text]
> Ken
> Thanks for the prompt reply. I will try and create a simple DAP from
> scratch.
> The only reason I was looking athe DAP approach was that not all users
> will
> have Access.
>
> Is there any other way that I can have an application on the company
> Intranet, Shared drive or Internet so that users without Access can use
> it.
>
> Thanks
>
> Chas
>
>
> "Ken Snell (MVP)" wrote:
>
>> I eschew using the wizard in ACCESS to convert a form to a DAP because
>> DAPs
>> are so different from forms that it's almost never successful at making a
>> usable DAP. In your case, I recommend that you build the DAP from
>> scratch.
>>
>> However, let me caution you -- DAPs are significantly different from
>> forms,
>> and things that work in forms usually don't work in DAPs. Also, DAPs use
>> VBScript, not VBA.
>>
>> --
>>
>> Ken Snell
>> <MS ACCESS MVP>
>>
>>
>> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
>> news:2B85A37C-4885-455D-B047-BF82BDB472AD[ at ]microsoft.com...
>> > Hello All,
>> > I am new to Access although a fairly experienced VBA developer. I have
>> > recently had Access Loaded onto my set. I am in the process of
>> > developing
>> > a
>> > small application that has three main forms.
>> >
>> > 1) Sign in Form
>> > 2) A form that asks user for input and process a few tables
>> > 3) The main form, this form leads to various processing of tables.
>> >
>> > The text boxes in all the forms are unbound as I populate the text
>> > boxes
>> > with the neccessary information. (This info is from Tables).
>> >
>> > I want this application to be run from our Intranet. The first problem
>> > is
>> > that I cannot save the forms as DAP. I keep getting the message that
>> > unbound
>> > Forms cannot be converted to XML (or some similar response).
>> >
>> > Am I understanding this message correctly, is this because my forms'
>> > text
>> > boxes do not have a Source (showing "unbound" in Design View?, I do not
>> > need
>> > them to have a source).
>> >
>> > Is there a way around this. I chose this approach as all users do not
>> > have
>> > Access on their sets.
>> >
>> > Thanks in advance for any suggestions.
>> >
>> > Chas
>>
>>
>>


Re: Not able to create a DAP from unbound form.
ChasAA 11.09.2006 07:28:01
Ken,

Thanks for your help so far, but now for what might be a really silly
question:
I created a DAP from scratch. Two text boxes and a command button.
When I go into the VBScript Editor I can see the area where I should place
code for the command button "on click". If I enter some simple code like
msgbox("Hello"), this is fine and works when I press the command button.
If I try to enter more of a routine such as

Sub test
Dim ....
dim ....
lblOne.text="Hello"
end Sub

This will generate an error.
So question is, can I write procedures in VBScript (The tutorial I have had
a look at show that I can). Can I call other procedures, and lastly can I
reference recordsets as that is my final aim.

From what I can see from various sources is that it is only possible to
"view" table data, some say it may be possible to edit records.

Would you have time to look at what I am trying to do and would you tell me
if it will be possible to do what I am trying to achieve or will I have to
look at a completely approach.

My email is charleschand[ at ]aol.com

Chas.

"Ken Snell (MVP)" wrote:

[Quoted Text]
> There is a runtime option for ACCESS that allows a person who has the
> license to create them the ability to create ACCESS applications that can be
> run by uses who don't have ACCESS installed on their PCs. This is not a part
> of the regular ACCESS software though, and must be purchased separately.
> What you need to purchase depends upon which version of ACCESS you would use
> to generate the runtime setup. Then you install the runtimes on each
> person's PCs.
>
> Otherwise, DAPs and ASPs (active server pages, using Internet Explorer)
> would be the methods for allowing use of ACCESS database by people who don't
> have ACCESS. Note that the users must have the Office Web Components
> installed on their PCs in order to use DAPs.
> --
>
> Ken Snell
> <MS ACCESS MVP>
>
>
>
>
> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
> news:AC626855-A0EA-4E9D-80E9-B3B2C9D1D7B0[ at ]microsoft.com...
> > Ken
> > Thanks for the prompt reply. I will try and create a simple DAP from
> > scratch.
> > The only reason I was looking athe DAP approach was that not all users
> > will
> > have Access.
> >
> > Is there any other way that I can have an application on the company
> > Intranet, Shared drive or Internet so that users without Access can use
> > it.
> >
> > Thanks
> >
> > Chas
> >
> >
> > "Ken Snell (MVP)" wrote:
> >
> >> I eschew using the wizard in ACCESS to convert a form to a DAP because
> >> DAPs
> >> are so different from forms that it's almost never successful at making a
> >> usable DAP. In your case, I recommend that you build the DAP from
> >> scratch.
> >>
> >> However, let me caution you -- DAPs are significantly different from
> >> forms,
> >> and things that work in forms usually don't work in DAPs. Also, DAPs use
> >> VBScript, not VBA.
> >>
> >> --
> >>
> >> Ken Snell
> >> <MS ACCESS MVP>
> >>
> >>
> >> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
> >> news:2B85A37C-4885-455D-B047-BF82BDB472AD[ at ]microsoft.com...
> >> > Hello All,
> >> > I am new to Access although a fairly experienced VBA developer. I have
> >> > recently had Access Loaded onto my set. I am in the process of
> >> > developing
> >> > a
> >> > small application that has three main forms.
> >> >
> >> > 1) Sign in Form
> >> > 2) A form that asks user for input and process a few tables
> >> > 3) The main form, this form leads to various processing of tables.
> >> >
> >> > The text boxes in all the forms are unbound as I populate the text
> >> > boxes
> >> > with the neccessary information. (This info is from Tables).
> >> >
> >> > I want this application to be run from our Intranet. The first problem
> >> > is
> >> > that I cannot save the forms as DAP. I keep getting the message that
> >> > unbound
> >> > Forms cannot be converted to XML (or some similar response).
> >> >
> >> > Am I understanding this message correctly, is this because my forms'
> >> > text
> >> > boxes do not have a Source (showing "unbound" in Design View?, I do not
> >> > need
> >> > them to have a source).
> >> >
> >> > Is there a way around this. I chose this approach as all users do not
> >> > have
> >> > Access on their sets.
> >> >
> >> > Thanks in advance for any suggestions.
> >> >
> >> > Chas
> >>
> >>
> >>
>
>
>
Re: Not able to create a DAP from unbound form.
"Ken Snell \(MVP\)" <kthsneisllis9[ at ]ncoomcastt.renaetl> 12.09.2006 02:49:06
I don't have time to volunteer to look at your database, sorry...work calls
first < g >.

Yes, you can edit data via a DAP, but it's more tricky than on a form
because queries more often are not updatable in a DAP than in a form, so
anything more than a two-table query often won't be updatable.

You can write VBScript subroutines and functions in a DAP's module. You put
them in the Head section of the module's code. You then can call them from
within the DAP's module. Easiest way to see where to put the script
procedures is to find the tag </HEAD> and put the script right above it.

Unfortunately, there is very limited debugging capability in VBScript
Editor, so errors in code are difficult to find without putting a MsgBox
after every script line to trace the script as it runs and to see where the
script errors and thus stops. VBScript is much more limited in its ability
to modify the content of a DAP once it's been loaded and opened, so I rarely
try to manipulate label, etc. elements' information from script.
--

Ken Snell
<MS ACCESS MVP>




"ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
news:42A727D4-6E4C-402D-AAED-EB7E89CE31DC[ at ]microsoft.com...
[Quoted Text]
> Ken,
>
> Thanks for your help so far, but now for what might be a really silly
> question:
> I created a DAP from scratch. Two text boxes and a command button.
> When I go into the VBScript Editor I can see the area where I should place
> code for the command button "on click". If I enter some simple code like
> msgbox("Hello"), this is fine and works when I press the command button.
> If I try to enter more of a routine such as
>
> Sub test
> Dim ....
> dim ....
> lblOne.text="Hello"
> end Sub
>
> This will generate an error.
> So question is, can I write procedures in VBScript (The tutorial I have
> had
> a look at show that I can). Can I call other procedures, and lastly can I
> reference recordsets as that is my final aim.
>
> From what I can see from various sources is that it is only possible to
> "view" table data, some say it may be possible to edit records.
>
> Would you have time to look at what I am trying to do and would you tell
> me
> if it will be possible to do what I am trying to achieve or will I have to
> look at a completely approach.
>
> My email is charleschand[ at ]aol.com
>
> Chas.
>
> "Ken Snell (MVP)" wrote:
>
>> There is a runtime option for ACCESS that allows a person who has the
>> license to create them the ability to create ACCESS applications that can
>> be
>> run by uses who don't have ACCESS installed on their PCs. This is not a
>> part
>> of the regular ACCESS software though, and must be purchased separately.
>> What you need to purchase depends upon which version of ACCESS you would
>> use
>> to generate the runtime setup. Then you install the runtimes on each
>> person's PCs.
>>
>> Otherwise, DAPs and ASPs (active server pages, using Internet Explorer)
>> would be the methods for allowing use of ACCESS database by people who
>> don't
>> have ACCESS. Note that the users must have the Office Web Components
>> installed on their PCs in order to use DAPs.
>> --
>>
>> Ken Snell
>> <MS ACCESS MVP>
>>
>>
>>
>>
>> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
>> news:AC626855-A0EA-4E9D-80E9-B3B2C9D1D7B0[ at ]microsoft.com...
>> > Ken
>> > Thanks for the prompt reply. I will try and create a simple DAP from
>> > scratch.
>> > The only reason I was looking athe DAP approach was that not all users
>> > will
>> > have Access.
>> >
>> > Is there any other way that I can have an application on the company
>> > Intranet, Shared drive or Internet so that users without Access can use
>> > it.
>> >
>> > Thanks
>> >
>> > Chas
>> >
>> >
>> > "Ken Snell (MVP)" wrote:
>> >
>> >> I eschew using the wizard in ACCESS to convert a form to a DAP because
>> >> DAPs
>> >> are so different from forms that it's almost never successful at
>> >> making a
>> >> usable DAP. In your case, I recommend that you build the DAP from
>> >> scratch.
>> >>
>> >> However, let me caution you -- DAPs are significantly different from
>> >> forms,
>> >> and things that work in forms usually don't work in DAPs. Also, DAPs
>> >> use
>> >> VBScript, not VBA.
>> >>
>> >> --
>> >>
>> >> Ken Snell
>> >> <MS ACCESS MVP>
>> >>
>> >>
>> >> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
>> >> news:2B85A37C-4885-455D-B047-BF82BDB472AD[ at ]microsoft.com...
>> >> > Hello All,
>> >> > I am new to Access although a fairly experienced VBA developer. I
>> >> > have
>> >> > recently had Access Loaded onto my set. I am in the process of
>> >> > developing
>> >> > a
>> >> > small application that has three main forms.
>> >> >
>> >> > 1) Sign in Form
>> >> > 2) A form that asks user for input and process a few tables
>> >> > 3) The main form, this form leads to various processing of tables.
>> >> >
>> >> > The text boxes in all the forms are unbound as I populate the text
>> >> > boxes
>> >> > with the neccessary information. (This info is from Tables).
>> >> >
>> >> > I want this application to be run from our Intranet. The first
>> >> > problem
>> >> > is
>> >> > that I cannot save the forms as DAP. I keep getting the message
>> >> > that
>> >> > unbound
>> >> > Forms cannot be converted to XML (or some similar response).
>> >> >
>> >> > Am I understanding this message correctly, is this because my forms'
>> >> > text
>> >> > boxes do not have a Source (showing "unbound" in Design View?, I do
>> >> > not
>> >> > need
>> >> > them to have a source).
>> >> >
>> >> > Is there a way around this. I chose this approach as all users do
>> >> > not
>> >> > have
>> >> > Access on their sets.
>> >> >
>> >> > Thanks in advance for any suggestions.
>> >> >
>> >> > Chas
>> >>
>> >>
>> >>
>>
>>
>>


Re: Not able to create a DAP from unbound form.
ChasAA 12.09.2006 05:43:01
Hello again Ken,
Thanks for the reply. It is okay and I understand that you are not able to
have a look at my database. (I only suggested that because I thought it
would be easier to see what I wqas trying to achieve).

Anyway I am fighting a losing battle I think.

Our system adminstrators have really "locked down" the system in as much
that we cannot install ANYTHING on our sets, they will not allow installation
of OWC which really menas that DAPS are out. We cannot even email each other
..MDB files.

The next approach will be to write an XLA adding with a reference to
Microsoft ActiveX Data Object and connect to the DB. Have tried an
experiment with this but have already come across a problem.

I can create and read recordsets (as in Access) but cannot Filter Sort or
Update them. Error : "This Provider does not have the neccesary interface
for Filter or Sort etc, (something to that effect anyway).

Any suggestions?

Thanks in advance

Chas

"Ken Snell (MVP)" wrote:

[Quoted Text]
> I don't have time to volunteer to look at your database, sorry...work calls
> first < g >.
>
> Yes, you can edit data via a DAP, but it's more tricky than on a form
> because queries more often are not updatable in a DAP than in a form, so
> anything more than a two-table query often won't be updatable.
>
> You can write VBScript subroutines and functions in a DAP's module. You put
> them in the Head section of the module's code. You then can call them from
> within the DAP's module. Easiest way to see where to put the script
> procedures is to find the tag </HEAD> and put the script right above it.
>
> Unfortunately, there is very limited debugging capability in VBScript
> Editor, so errors in code are difficult to find without putting a MsgBox
> after every script line to trace the script as it runs and to see where the
> script errors and thus stops. VBScript is much more limited in its ability
> to modify the content of a DAP once it's been loaded and opened, so I rarely
> try to manipulate label, etc. elements' information from script.
> --
>
> Ken Snell
> <MS ACCESS MVP>
>
>
>
>
> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
> news:42A727D4-6E4C-402D-AAED-EB7E89CE31DC[ at ]microsoft.com...
> > Ken,
> >
> > Thanks for your help so far, but now for what might be a really silly
> > question:
> > I created a DAP from scratch. Two text boxes and a command button.
> > When I go into the VBScript Editor I can see the area where I should place
> > code for the command button "on click". If I enter some simple code like
> > msgbox("Hello"), this is fine and works when I press the command button.
> > If I try to enter more of a routine such as
> >
> > Sub test
> > Dim ....
> > dim ....
> > lblOne.text="Hello"
> > end Sub
> >
> > This will generate an error.
> > So question is, can I write procedures in VBScript (The tutorial I have
> > had
> > a look at show that I can). Can I call other procedures, and lastly can I
> > reference recordsets as that is my final aim.
> >
> > From what I can see from various sources is that it is only possible to
> > "view" table data, some say it may be possible to edit records.
> >
> > Would you have time to look at what I am trying to do and would you tell
> > me
> > if it will be possible to do what I am trying to achieve or will I have to
> > look at a completely approach.
> >
> > My email is charleschand[ at ]aol.com
> >
> > Chas.
> >
> > "Ken Snell (MVP)" wrote:
> >
> >> There is a runtime option for ACCESS that allows a person who has the
> >> license to create them the ability to create ACCESS applications that can
> >> be
> >> run by uses who don't have ACCESS installed on their PCs. This is not a
> >> part
> >> of the regular ACCESS software though, and must be purchased separately.
> >> What you need to purchase depends upon which version of ACCESS you would
> >> use
> >> to generate the runtime setup. Then you install the runtimes on each
> >> person's PCs.
> >>
> >> Otherwise, DAPs and ASPs (active server pages, using Internet Explorer)
> >> would be the methods for allowing use of ACCESS database by people who
> >> don't
> >> have ACCESS. Note that the users must have the Office Web Components
> >> installed on their PCs in order to use DAPs.
> >> --
> >>
> >> Ken Snell
> >> <MS ACCESS MVP>
> >>
> >>
> >>
> >>
> >> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
> >> news:AC626855-A0EA-4E9D-80E9-B3B2C9D1D7B0[ at ]microsoft.com...
> >> > Ken
> >> > Thanks for the prompt reply. I will try and create a simple DAP from
> >> > scratch.
> >> > The only reason I was looking athe DAP approach was that not all users
> >> > will
> >> > have Access.
> >> >
> >> > Is there any other way that I can have an application on the company
> >> > Intranet, Shared drive or Internet so that users without Access can use
> >> > it.
> >> >
> >> > Thanks
> >> >
> >> > Chas
> >> >
> >> >
> >> > "Ken Snell (MVP)" wrote:
> >> >
> >> >> I eschew using the wizard in ACCESS to convert a form to a DAP because
> >> >> DAPs
> >> >> are so different from forms that it's almost never successful at
> >> >> making a
> >> >> usable DAP. In your case, I recommend that you build the DAP from
> >> >> scratch.
> >> >>
> >> >> However, let me caution you -- DAPs are significantly different from
> >> >> forms,
> >> >> and things that work in forms usually don't work in DAPs. Also, DAPs
> >> >> use
> >> >> VBScript, not VBA.
> >> >>
> >> >> --
> >> >>
> >> >> Ken Snell
> >> >> <MS ACCESS MVP>
> >> >>
> >> >>
> >> >> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
> >> >> news:2B85A37C-4885-455D-B047-BF82BDB472AD[ at ]microsoft.com...
> >> >> > Hello All,
> >> >> > I am new to Access although a fairly experienced VBA developer. I
> >> >> > have
> >> >> > recently had Access Loaded onto my set. I am in the process of
> >> >> > developing
> >> >> > a
> >> >> > small application that has three main forms.
> >> >> >
> >> >> > 1) Sign in Form
> >> >> > 2) A form that asks user for input and process a few tables
> >> >> > 3) The main form, this form leads to various processing of tables.
> >> >> >
> >> >> > The text boxes in all the forms are unbound as I populate the text
> >> >> > boxes
> >> >> > with the neccessary information. (This info is from Tables).
> >> >> >
> >> >> > I want this application to be run from our Intranet. The first
> >> >> > problem
> >> >> > is
> >> >> > that I cannot save the forms as DAP. I keep getting the message
> >> >> > that
> >> >> > unbound
> >> >> > Forms cannot be converted to XML (or some similar response).
> >> >> >
> >> >> > Am I understanding this message correctly, is this because my forms'
> >> >> > text
> >> >> > boxes do not have a Source (showing "unbound" in Design View?, I do
> >> >> > not
> >> >> > need
> >> >> > them to have a source).
> >> >> >
> >> >> > Is there a way around this. I chose this approach as all users do
> >> >> > not
> >> >> > have
> >> >> > Access on their sets.
> >> >> >
> >> >> > Thanks in advance for any suggestions.
> >> >> >
> >> >> > Chas
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
Re: Not able to create a DAP from unbound form.
"Ken Snell \(MVP\)" <kthsneisllis9[ at ]ncoomcastt.renaetl> 13.09.2006 01:42:09
Can't email .mdb files? Amazing how IT departments can be so dictatorial --
do they wonder why no work ever gets done?

By xla, I assume you mean trying to manipulate data in ACCESS via EXCEL? If
yes, I don't believe you can do this any more. Updates to Office XP and
Office 2003 have taken the ability of ACCESS and EXCEL to link and update
each others' data. So this approach is probably doomed.

OWC is part of Office installation, typically, so it may already be
installed on people's PCs if they have Office.

Other than that, sounds like it's time to stage a Boston Tea Party on your
IT group.... < smile >
--

Ken Snell
<MS ACCESS MVP>




"ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
news:24B5BCB6-4637-4198-920F-00CA6502FB32[ at ]microsoft.com...
[Quoted Text]
> Hello again Ken,
> Thanks for the reply. It is okay and I understand that you are not able
> to
> have a look at my database. (I only suggested that because I thought it
> would be easier to see what I wqas trying to achieve).
>
> Anyway I am fighting a losing battle I think.
>
> Our system adminstrators have really "locked down" the system in as much
> that we cannot install ANYTHING on our sets, they will not allow
> installation
> of OWC which really menas that DAPS are out. We cannot even email each
> other
> .MDB files.
>
> The next approach will be to write an XLA adding with a reference to
> Microsoft ActiveX Data Object and connect to the DB. Have tried an
> experiment with this but have already come across a problem.
>
> I can create and read recordsets (as in Access) but cannot Filter Sort or
> Update them. Error : "This Provider does not have the neccesary interface
> for Filter or Sort etc, (something to that effect anyway).
>
> Any suggestions?
>
> Thanks in advance
>
> Chas
>
> "Ken Snell (MVP)" wrote:
>
>> I don't have time to volunteer to look at your database, sorry...work
>> calls
>> first < g >.
>>
>> Yes, you can edit data via a DAP, but it's more tricky than on a form
>> because queries more often are not updatable in a DAP than in a form, so
>> anything more than a two-table query often won't be updatable.
>>
>> You can write VBScript subroutines and functions in a DAP's module. You
>> put
>> them in the Head section of the module's code. You then can call them
>> from
>> within the DAP's module. Easiest way to see where to put the script
>> procedures is to find the tag </HEAD> and put the script right above it.
>>
>> Unfortunately, there is very limited debugging capability in VBScript
>> Editor, so errors in code are difficult to find without putting a MsgBox
>> after every script line to trace the script as it runs and to see where
>> the
>> script errors and thus stops. VBScript is much more limited in its
>> ability
>> to modify the content of a DAP once it's been loaded and opened, so I
>> rarely
>> try to manipulate label, etc. elements' information from script.
>> --
>>
>> Ken Snell
>> <MS ACCESS MVP>
>>
>>
>>
>>
>> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
>> news:42A727D4-6E4C-402D-AAED-EB7E89CE31DC[ at ]microsoft.com...
>> > Ken,
>> >
>> > Thanks for your help so far, but now for what might be a really silly
>> > question:
>> > I created a DAP from scratch. Two text boxes and a command button.
>> > When I go into the VBScript Editor I can see the area where I should
>> > place
>> > code for the command button "on click". If I enter some simple code
>> > like
>> > msgbox("Hello"), this is fine and works when I press the command
>> > button.
>> > If I try to enter more of a routine such as
>> >
>> > Sub test
>> > Dim ....
>> > dim ....
>> > lblOne.text="Hello"
>> > end Sub
>> >
>> > This will generate an error.
>> > So question is, can I write procedures in VBScript (The tutorial I have
>> > had
>> > a look at show that I can). Can I call other procedures, and lastly
>> > can I
>> > reference recordsets as that is my final aim.
>> >
>> > From what I can see from various sources is that it is only possible to
>> > "view" table data, some say it may be possible to edit records.
>> >
>> > Would you have time to look at what I am trying to do and would you
>> > tell
>> > me
>> > if it will be possible to do what I am trying to achieve or will I have
>> > to
>> > look at a completely approach.
>> >
>> > My email is charleschand[ at ]aol.com
>> >
>> > Chas.
>> >
>> > "Ken Snell (MVP)" wrote:
>> >
>> >> There is a runtime option for ACCESS that allows a person who has the
>> >> license to create them the ability to create ACCESS applications that
>> >> can
>> >> be
>> >> run by uses who don't have ACCESS installed on their PCs. This is not
>> >> a
>> >> part
>> >> of the regular ACCESS software though, and must be purchased
>> >> separately.
>> >> What you need to purchase depends upon which version of ACCESS you
>> >> would
>> >> use
>> >> to generate the runtime setup. Then you install the runtimes on each
>> >> person's PCs.
>> >>
>> >> Otherwise, DAPs and ASPs (active server pages, using Internet
>> >> Explorer)
>> >> would be the methods for allowing use of ACCESS database by people who
>> >> don't
>> >> have ACCESS. Note that the users must have the Office Web Components
>> >> installed on their PCs in order to use DAPs.
>> >> --
>> >>
>> >> Ken Snell
>> >> <MS ACCESS MVP>
>> >>
>> >>
>> >>
>> >>
>> >> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
>> >> news:AC626855-A0EA-4E9D-80E9-B3B2C9D1D7B0[ at ]microsoft.com...
>> >> > Ken
>> >> > Thanks for the prompt reply. I will try and create a simple DAP
>> >> > from
>> >> > scratch.
>> >> > The only reason I was looking athe DAP approach was that not all
>> >> > users
>> >> > will
>> >> > have Access.
>> >> >
>> >> > Is there any other way that I can have an application on the company
>> >> > Intranet, Shared drive or Internet so that users without Access can
>> >> > use
>> >> > it.
>> >> >
>> >> > Thanks
>> >> >
>> >> > Chas
>> >> >
>> >> >
>> >> > "Ken Snell (MVP)" wrote:
>> >> >
>> >> >> I eschew using the wizard in ACCESS to convert a form to a DAP
>> >> >> because
>> >> >> DAPs
>> >> >> are so different from forms that it's almost never successful at
>> >> >> making a
>> >> >> usable DAP. In your case, I recommend that you build the DAP from
>> >> >> scratch.
>> >> >>
>> >> >> However, let me caution you -- DAPs are significantly different
>> >> >> from
>> >> >> forms,
>> >> >> and things that work in forms usually don't work in DAPs. Also,
>> >> >> DAPs
>> >> >> use
>> >> >> VBScript, not VBA.
>> >> >>
>> >> >> --
>> >> >>
>> >> >> Ken Snell
>> >> >> <MS ACCESS MVP>
>> >> >>
>> >> >>
>> >> >> "ChasAA" <ChasAA[ at ]discussions.microsoft.com> wrote in message
>> >> >> news:2B85A37C-4885-455D-B047-BF82BDB472AD[ at ]microsoft.com...
>> >> >> > Hello All,
>> >> >> > I am new to Access although a fairly experienced VBA developer.
>> >> >> > I
>> >> >> > have
>> >> >> > recently had Access Loaded onto my set. I am in the process of
>> >> >> > developing
>> >> >> > a
>> >> >> > small application that has three main forms.
>> >> >> >
>> >> >> > 1) Sign in Form
>> >> >> > 2) A form that asks user for input and process a few tables
>> >> >> > 3) The main form, this form leads to various processing of
>> >> >> > tables.
>> >> >> >
>> >> >> > The text boxes in all the forms are unbound as I populate the
>> >> >> > text
>> >> >> > boxes
>> >> >> > with the neccessary information. (This info is from Tables).
>> >> >> >
>> >> >> > I want this application to be run from our Intranet. The first
>> >> >> > problem
>> >> >> > is
>> >> >> > that I cannot save the forms as DAP. I keep getting the message
>> >> >> > that
>> >> >> > unbound
>> >> >> > Forms cannot be converted to XML (or some similar response).
>> >> >> >
>> >> >> > Am I understanding this message correctly, is this because my
>> >> >> > forms'
>> >> >> > text
>> >> >> > boxes do not have a Source (showing "unbound" in Design View?, I
>> >> >> > do
>> >> >> > not
>> >> >> > need
>> >> >> > them to have a source).
>> >> >> >
>> >> >> > Is there a way around this. I chose this approach as all users
>> >> >> > do
>> >> >> > not
>> >> >> > have
>> >> >> > Access on their sets.
>> >> >> >
>> >> >> > Thanks in advance for any suggestions.
>> >> >> >
>> >> >> > Chas
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>


Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net