Inside of Oracle Sql *plus
i use the commands alter table tablename
modify columname varchar2(10)
;

to change the field size to 10

When I open up Access to view the linked table via an odbc connection,
in the design view, it still shows the field as having a field size
of 5.

What did I miss.

This is all tied to a web app, where, I changed all of the web forms
to accept 10 characters.....

On 24.03.2009 19:20, BookerT wrote:
Probably the refresh button in Access.

You have tied MS Access into a web app which also uses Oracle? That
sounds spooky.

Your question sounds more suitable for a MS Access specific forum. Even
there you should probably include the version of Access.

Good luck!

robert

On Mar 24, 2:45*pm, Robert Klemme <shortcut... (AT) googlemail (DOT) com> wrote:
Thanks...

no the web app is tied to oracle, but since it is an oracle databse,
sometimes, I will use Access (2007) to look at the database instead of
Oracle. Remember, I am just using the ODBC connection to make a link
to the tables...... thast is the only use for Access........

Refresh should not be an issue because I made the change yesterday,
and opened up a new conection to it today, so it should show the
updated value

But I hit refresh anyway, and no change. I wanted to make sure I
covered all of the oracle bases. if Oracle shows it as varchar2(10)
then it should allow 10 characters correct?

Another footnote. In my web app, I put in a digit in that field that
was bigger than 5 characters, but sure enough when I look at the
linked table in Access, it only shows 5 characters as the field limit
suggessts

Thanks

On Mar 24, 2:54*pm, BookerT <ch... (AT) mierbo (DOT) com> wrote:
Never mind, once I created a "new" database and relinked the tables,
it showed the updated field length size. Why a refresh did not do
that, I am not sure?

On Mar 24, 3:31*pm, BookerT <ch... (AT) mierbo (DOT) com> wrote:
The definition for the linked table in Access did not change when you
changed the source definition in Oracle.


David Fitzjarrell

On 24.03.2009 21:36, ddf wrote:
OP, this is probably the time to switch to better tools than MS Access
(SQL Plus and SQL Developer come to mind).

Cheers

robert

--
remember.guy do |as, often| as.you_can - without end

On Mar 24, 2:45*pm, Robert Klemme <shortcut... (AT) googlemail (DOT) com> wrote:
Robert, the other basic thing that we missed, is I did not use the
commit work; command and that seemed to make a difference as well. So
it was not an Access problem, but a SQL issue, .. does that make sense?

BookerT (chipw (AT) mierbo (DOT) com) wrote:
: On Mar 24, 2:45=A0pm, Robert Klemme <shortcut... (AT) googlemail (DOT) com> wrote:
: > On 24.03.2009 19:20, BookerT wrote:
: >
: > > Inside of Oracle Sql *plus
: > > =A0 i use the commands alter table tablename
: > > modify =A0columname varchar2(10)
: > > ;
: >
: > > to change the field size to 10
: >
: > > When I open up Access to view the linked table via an odbc connection,
: > > in the design view, it still shows the field =A0as having a field size
: > > of 5.
: >
: > > What did I miss.
: >
: > Probably the refresh button in Access.
: >
: > > This is all tied to a web app, where, I changed all of the web forms
: > > to accept 10 characters.....
: >
: > You have tied MS Access into a web app which also uses Oracle? =A0That
: > sounds spooky.
: >
: > Your question sounds more suitable for a MS Access specific forum. =A0Eve=
: n
: > there you should probably include the version of Access.
: >
: > Good luck!
: >
: > =A0 =A0 =A0 =A0 robert

: Robert, the other basic thing that we missed, is I did not use the
: commit work; command and that seemed to make a difference as well. So
: it was not an Access problem, but a SQL issue, .. does that make sense?


Access stores details about the linked table. The only issue is the
correct/best way to force Access to update its local version of those
details.

On Mar 24, 1:31*pm, BookerT <ch... (AT) mierbo (DOT) com> wrote:
Doing a quick google on access refresh, looks like it only refreshes
the data, not the metadata. cf http://msdn.microsoft.com/en-us/library/bb238065.aspx

In the Oracle world, it has long been a basic DBA habit to not change
metadata while people are accessing data. Any DDL does a commit
before and after the DDL, which kinda gets past a lot of potential
problems, so some people do it anyways, and there are exceptions with
certain DDL commands, truncate comes to mind. Any particular
application may not be happy with this, especially if it is not
written with an Oracle world-view in mind.

Of course, nowadays my car changes the number of cylinders it uses
while I'm driving - a feature with notable $ advantages, not a bug.
It's a brave new world.

jg
--
@home.com is bogus.
Weird spelling propagates from google code... http://www.google.com/search?hl=en&q=Permalnik+

On Tue, 24 Mar 2009 14:40:34 -0700 (PDT), BookerT <chipw (AT) mierbo (DOT) com>
wrote:

It makes no sense at all, as every DDL is automatically committed.
You really need some knowledge brushing up.
As soon as you change any table in Oracle, you'll need to *reattach*
it in Access, or the changed definition will not show up.
So it IS an Access problem, and a problem with your lack of knowledge.

--
Sybrand Bakker
Senior Oracle DBA